Method and apparatus for capacity exchange

ABSTRACT

Methods, systems, and apparatuses are described for fault tolerant network storage and delivery of recorded content. Two or more network digital video recorders may each receive a plurality of requests to record, archive, and/or play back content items, such as television programs. Each network digital video recorder may receive capacity reports of statistics such as storage and/or bandwidth from one or more other network digital video recorders. At least one of the network digital video recorders may determine whether, based on a network capacity, to record, archive, and/or playback content items. The methods, systems, and apparatuses may accommodate equipment failures that lead to partitions between network digital video recorders.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/165,473, filed Oct. 19, 2018, which is a continuation-in-part of U.S.patent application Ser. No. 14/730,519, filed Jun. 4, 2015, each ofwhich is hereby incorporated by reference in their entirety.

BACKGROUND

Network digital video recorders (nDVRs) may be useful tools in recordingscheduled video content for users to watch at a more convenient time,but operating a network of nDVRs may require substantial processing andresources. It is possible for nDVRs to become overburdened and/or fail,and degrade the users' overall experience using nDVRs. Solutions thatadd one or more load balancers between a content source and the nDVRs donot resolve issues associated with connectivity failures, as the loadbalancers become possible points of failure.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for fault tolerantnetwork storage and delivery of recorded content. Two or more nDVRs maybe located at respective data centers with each nDVR receiving aplurality of requests to record content. The nDVRs in the data centersmay include capacity exchange servers that compile and exchange capacityinformation. A capacity exchange server of each data center's nDVR maypoll one or more components in the nDVR for their current utilization.The utilization information may be compiled into one or more messagesthat may be exchanged with one or more capacity exchange servers amongthe data centers. From that exchanged capacity information, the nDVRsmay each determine where to record, where to archive, and/or where toreconstitute content items or segments of content items. Based on theavailable capacity across the group of nDVRs, programs or segments ofprograms may be recorded by one or more nDVRs and/or deduplicated.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example communication network.

FIG. 2 shows hardware elements of a computing device.

FIG. 3 shows an example of an arrangement of two nDVRs with capacityexchange servers.

FIG. 4 shows an example of an arrangement of three nDVRs with capacityexchange servers.

FIG. 5A is a flow chart showing an example method for exchangingcapacity data between nDVRs.

FIG. 5B is a flow chart showing an example method for combining capacitydata.

FIG. 6 is a flow chart showing an example method for determining whereto record segments.

FIGS. 7A-7C show examples of factors considered during determinationswhere segments are to be recorded, archived, and/or reconstituted.

FIG. 8 shows an example of a timeline indicating from where content isplayed back for users.

FIG. 9 shows examples of information used to determine the recordinglocations in the timeline of FIG. 8.

FIG. 10 shows examples of values and weighting factors used to determinewhere to record segments.

FIG. 11 is a flow chart showing an example of a method for archivingand/or reconstituting segments.

FIG. 12 shows examples of information used to determine where to archivethe segments of FIG. 11.

FIG. 13 shows examples of values and weighting factors used to determinewhere to archive segments.

FIG. 14 shows examples of information used to determine where toreconstitute the segments of FIG. 11.

FIG. 15 shows examples of values and weighting factors used to determinewhere to reconstitute segments for playback.

FIG. 16 shows an example nDVR system with a capacity exchange server.

FIG. 17 is a flow chart showing an example method for recordingsegments.

FIGS. 18A-18C show example representations of recordings of contentitems.

FIG. 19 is a flow chart showing an example method for deliveringsegments.

FIG. 20 shows example representations of recordings of content items.

DETAILED DESCRIPTION

The accompanying drawings, which form a part hereof, show examples ofthe disclosure. It is to be understood that the examples shown in thedrawings and/or discussed herein are non-exclusive and that there areother examples of how the disclosure may be practiced.

In addition, the phraseology and terminology used herein are for thepurpose of description and should not be regarded as limiting. Rather,the phrases and terms used herein are to be given their broadestinterpretation and meaning.

Fault tolerant capacity management may be used in connection withrecording content for users. Content may comprise video and/or audioprograms available from a content provider. A content item may comprisea specific video and/or audio program. The content item may comprise oneor more segments. Based on various restrictions, a separate copy of acontent item may be recorded for each user that requests content to bestored by an nDVR. Two or more nDVRs may operate together by exchangingcapacity information and determining where to record content based onthe exchanged capacity information.

A first segment from the plurality of segments may be recorded in afirst storage, such as a recording storage (on a hard drive) of a datacenter. A second segment may be recorded in a second storage of anotherdata center. The first and second segments may be consolidated at alater time in one of the data centers or in yet another data center.

The segmented nature of content may be leveraged to facilitate thestorage and delivery of the content using different nDVRs in differentdata centers. Multiple requests from multiple users to record aparticular content item show may be received. A unique copy of thecontent item may be generated and stored for each of the requestingusers (e.g., by a recording management system). During recording of thecontent item, multiple copies of each segment may be generated. Asegment of the content item may be selected, and a specific mediarecorder server may be selected to record that segment. That mediarecorder server or another media recorder server may be selected togenerate a copy of the segment in a recording storage for each of therequesting users. The media recorder server may perform a single accessof the segment and direct the recording storage to generate the multiplecopies of the segment in a single write operation and/or may performmultiple accesses of the segment and direct the storage to generateportions of the copies at different times. The copies of the segment maybe written to a hard disk or solid-state memory of the recording storagein sequence. The method may be repeated for each segment of the contentitem until a complete unique copy of the content item exists in therecording storage for each requesting user. Where a user wishes to viewthe recorded content item, the user's unique copy in the recordingstorage may be delivered to that user's device for viewing.

nDVRs in different data centers may communicate their respectivecapacity to each other. Based on the exchanged capacity informationand/or possibly other information, each nDVR may determine whether itshould record or not record incoming segments. Based on updated capacityinformation, each nDVR may determine whether its recorded segmentsshould be archived locally, forwarded to another nDVR, and/or deleted.Further, each nDVR may determine where archived content should bereconstituted for playback to a user (e.g., retrieved from an archiveand stored in a form available for playback). Each nDVR mayindependently arrive at a conclusion of which segments to record and/orwhich not to record. The conclusions of the nDVRs need not be shared, aseach may arrive at the same conclusion(s) of where each segment shouldbe recorded. Using one or more of these approaches, network trafficcommonly associated with load balancers may be reduced.

The recording capacity of an nDVR may be based on one or more of thefollowing: network bandwidth, processing power, and/or availablestorage. Based on measurements for one or more of these parametersdropping below an expected level of service, an nDVR may be identifiedand/or indicated as being over-capacity or, if unavailable, partitionedfrom the rest of the network. For explanatory purposes, the state of annDVR of a first data center being off-line or no longer communicatingwith other nDVRs of other data centers may be referred to as“partitioned” from the other nDVRs.

Capacity information for an nDVR may be indicated by one or more of thefollowing values: a current quantity of recording requests being handledby one or more media storage servers in an nDVR; a maximum quantity ofrecording requests that may be handled by the one or more media storageservers in the nDVR; a current quantity of playback requests beinghandled by the one or more media storage servers in the nDVR; a maximumquantity of playback requests that may be handled by the one or moremedia storage servers in the nDVR; a current server load of internal,disk-related traffic in the nDVR; a maximum server load of internal,disk-related traffic in the nDVR; a current server load of theprocessing of record and playback requests in the nDVR; or a maximumserver load of the processing of record and/or playback requests in thenDVR.

A capacity exchange server may poll the components of its local nDVR andcompile the received information as its local capacity data. Thecapacity exchange server may forward its local capacity data to othercapacity exchange servers of other nDVRs and likewise receive capacitydata from those other capacity exchange servers. The capacity exchangeserver may compile its local capacity data with the capacity data fromthe other capacity exchange servers to generate a current picture ofcapacity data across the combination of nDVRs in the responding datacenters. The current capacity information of the network may be used bythe nDVRs to determine one or more of whether to record segments,whether to archive recorded segments, and/or whether to reconstitutearchived segments. Some or all operations described as being performedby separate computing devices of an nDVR (e.g., different servers andother computing devices of FIGS. 3 and 4 below) may be performed by asingle computing device.

FIG. 1 shows an example communication network 100 in which featuresdescribed herein may be implemented. The communication network 100 maycomprise one or more information distribution networks of any type, suchas, without limitation, a telephone network, a wireless network (e.g.,an LTE network, a 5G network, a WiFi IEEE 802.11 network, a WiMAXnetwork, a satellite network, and/or any other network for wirelesscommunication), an optical fiber network, a coaxial cable network,and/or a hybrid fiber/coax distribution network. The communicationnetwork 100 may use a series of interconnected communication links 101(e.g., coaxial cables, optical fibers, wireless links, etc.) to connectmultiple premises 102 (e.g., businesses, homes, consumer dwellings,train stations, airports, etc.) to a local office 103 (e.g., a headend).The local office 103 may send downstream information signals and receiveupstream information signals via the communication links 101. Each ofthe premises 102 may comprise devices, described below, to receive,send, and/or otherwise process those signals and information containedtherein.

The communication links 101 may originate from the local office 103 andmay comprise components not illustrated, such as splitters, filters,amplifiers, etc., to help convey signals clearly. The communicationlinks 101 may be coupled to one or more wireless access points 127configured to communicate with one or more mobile devices 125 via one ormore wireless networks. The mobile devices 125 may comprise smartphones, tablets or laptop computers with wireless transceivers, tabletsor laptop computers in communication with other devices with wirelesstransceivers, and/or any other type of device configured to communicatevia a wireless network.

The local office 103 may comprise an interface 104, such as atermination system (TS). The interface 104 may comprise a cable modemtermination system (CMTS) and/or other computing device(s) configured tosend information downstream to, and to receive information upstreamfrom, devices communicating with the local office 103 via thecommunications links 101. The interface 104 may be configured to managecommunications among those devices, to manage communications betweenthose devices and backend devices such as servers 105-107, and/or tomanage communications between those devices and one or more externalnetworks 109. The local office 103 may comprise one or more networkinterfaces 108 that comprise circuitry needed to communicate via theexternal networks 109. The external networks 109 may comprise networksof Internet devices, telephone networks, wireless networks, wirelessnetworks, fiber optic networks, and/or any other desired network. Thelocal office 103 may also or alternatively communicate with the mobiledevices 125 via the interface 108 and one or more of the externalnetworks 109, e.g., via one or more of the wireless access points 127.

The push notification server 105 may be configured to generate pushnotifications to deliver information to devices in the premises 102and/or to the mobile devices 125. The content server 106 may beconfigured to provide content to devices in the premises 102 and/or tothe mobile devices 125. This content may comprise, for example, video,audio, text, web pages, images, files, etc. The content server 106 (or,alternatively, an authentication server) may comprise software tovalidate user identities and entitlements, to locate and retrieverequested content, and/or to initiate delivery (e.g., streaming) of thecontent. The application server 107 may be configured to offer anydesired service. For example, an application server may be responsiblefor collecting, and generating a download of, information for electronicprogram guide listings. Another application server may be responsiblefor monitoring user viewing habits and collecting information from thatmonitoring for use in selecting advertisements. Yet another applicationserver may be responsible for formatting and inserting advertisements ina video stream being transmitted to devices in the premises 102 and/orto the mobile devices 125. The local office 103 may comprise additionalservers, additional push, content, and/or application servers, and/orother types of servers. Although shown separately, the push server 105,the content server 106, and the application server 107, and/or otherserver(s) may be combined. The servers 105, 106, and 107, and/or otherservers, may be computing devices and may comprise memory storing dataand also storing computer executable instructions that, when executed byone or more processors, cause the server(s) to perform steps describedherein.

An example premises 102 a may comprise an interface 120. The interface120 may comprise circuitry used to communicate via the communicationlinks 101. The interface 120 may comprise a modem 110, which maycomprise transmitters and receivers used to communicate via thecommunication links 101 with the local office 103. The modem 110 maycomprise, for example, a coaxial cable modem (for coaxial cable lines ofthe communication links 101), a fiber interface node (for fiber opticlines of the communication links 101), a twisted-pair telephone modem, awireless transceiver, and/or any other desired modem device. One modemis shown in FIG. 1, but a plurality of modems operating in parallel maybe implemented within the interface 120. The interface 120 may comprisea gateway 111. The modem 110 may be connected to, or be a part of, thegateway 111. The gateway 111 may be a computing device that communicateswith the modem(s) 110 to allow one or more other devices in the premises102 a to communicate with the local office 103 and/or with other devicesbeyond the local office 103 (e.g., via the local office 103 and theexternal network(s) 109). The gateway 111 may comprise a set-top box(STB), digital video recorder (DVR), a digital transport adapter (DTA),a computer server, and/or any other desired computing device.

The gateway 111 may also comprise one or more local network interfacesto communicate, via one or more local networks, with devices in thepremises 102 a. Such devices may comprise, e.g., display devices 112(e.g., televisions), STBs or DVRs 113, personal computers 114, laptopcomputers 115, wireless devices 116 (e.g., wireless routers, wirelesslaptops, notebooks, tablets and netbooks, cordless phones (e.g., DigitalEnhanced Cordless Telephone—DECT phones), mobile phones, mobiletelevisions, personal digital assistants (PDA)), landline phones 117(e.g. Voice over Internet Protocol—VoIP phones), and any other desireddevices. Example types of local networks comprise Multimedia Over CoaxAlliance (MoCA) networks, Ethernet networks, networks communicating viaUniversal Serial Bus (USB) interfaces, wireless networks (e.g., IEEE802.11, IEEE 802.15, Bluetooth), networks communicating via in-premisespower lines, and others. The lines connecting the interface 120 with theother devices in the premises 102 a may represent wired or wirelessconnections, as may be appropriate for the type of local network used.One or more of the devices at the premises 102 a may be configured toprovide wireless communications channels (e.g., IEEE 802.11 channels) tocommunicate with one or more of the mobile devices 125, which may be on-or off-premises.

The mobile devices 125, one or more of the devices in the premises 102a, and/or other devices may receive, store, output, and/or otherwise useassets. An asset may comprise a video, a game, one or more images,software, audio, text, webpage(s), and/or other content.

Further, one or more service providers 118 may be connected to thenetwork 109. The service provider 118 may provide video-on-demand,streaming content, linear content, Voice over Internet Protocol (VoIP)telephony, and/or other services. The service provider 118 may includeone or more gateways 119 connected to one or more servers 120 to providethe services desired by users at the premises 102. To provide thoseservices, the service provider 118 may use the gateways 119 to managethe requests from the premises 102 for services provided by the one ormore servers 120.

In FIG. 1, the service provider 118 is shown with the gateway 119located at a common location with the server 120. The gateway 119 mayalso or alternatively be located remote from the server 120.Additionally or alternatively, while the service provider 118 is shownindirectly connected to the local office 103 via the network 109, theservice provider 118 may be directly connected to the local office 103as shown by a dashed line connecting the local office 103 to the serviceprovider 118, that is, without connecting via the network 109.

FIG. 2 shows hardware elements of a computing device 200 that may beused to implement any of the computing devices shown in FIG. 1 (e.g.,the mobile devices 125, any of the devices shown in the premises 102 a,any of the devices shown in the local office 103, any of the wirelessaccess points 127, any devices with the external network 109, any of thedevices associated with the service provider 118) and any othercomputing devices discussed herein (e.g., channel monitor servers, mediarecorder servers, media storage, capacity exchange servers, archiveservers, reconstitution servers, and guide scheduling servers). Thecomputing device 200 may comprise one or more processors 201, which mayexecute instructions of a computer program to perform any of thefunctions described herein. The instructions may be stored in aread-only memory (ROM) 202, random access memory (RAM) 203, removablemedia 204 (e.g., a USB drive, a compact disk (CD), a digital versatiledisk (DVD)), and/or in any other type of computer-readable medium ormemory. Instructions may also be stored in an attached (or internal)hard drive 205 or other types of storage media. The computing device 200may comprise one or more output devices, such as a display device 206(e.g., an external television and/or other external or internal displaydevice) and a speaker 214, and may comprise one or more output devicecontrollers 207, such as a video processor. One or more user inputdevices 208 may comprise a remote control, a keyboard, a mouse, a touchscreen (which may be integrated with the display device 206), amicrophone, etc. The computing device 200 may also comprise one or morenetwork interfaces, such as a network input/output (I/O) interface 210(e.g., a network card) to communicate with an external network 209. Thenetwork I/O interface 210 may be a wired interface (e.g., electrical, RF(via coax), optical (via fiber)), a wireless interface, or a combinationof the two. The network I/O interface 210 may comprise a modemconfigured to communicate via the external network 209. The externalnetwork 209 may comprise the communication links 101 discussed above,the external network 109, an in-home network, a network provider'swireless, coaxial, fiber, or hybrid fiber/coaxial distribution system(e.g., a DOCSIS network), or any other desired network. The computingdevice 200 may comprise a location-detecting device, such as a globalpositioning system (GPS) microprocessor 211, which may be configured toreceive and process global positioning signals and determine, withpossible assistance from an external server and antenna, a geographicposition of the computing device 200.

Although FIG. 2 shows an example hardware configuration, one or more ofthe elements of the computing device 200 may be implemented as softwareor a combination of hardware and software. Modifications may be made toadd, remove, combine, divide, etc. components of the computing device200. Additionally, the elements shown in FIG. 2 may be implemented usingbasic computing devices and components that have been configured toperform operations such as are described herein. For example, a memoryof the computing device 200 may store computer-executable instructionsthat, when executed by the processor 201 and/or one or more otherprocessors of the computing device 200, cause the computing device 200to perform one, some, or all operations described herein. Such memoryand processor(s) may also or alternatively be implemented through one ormore Integrated Circuits (ICs). The IC may be, for example, amicroprocessor that accesses programming instructions or other datastored in a ROM and/or hardwired into the IC. For example, the IC maycomprise an Application Specific Integrated Circuit (ASIC) having gatesand/or other logic dedicated to the calculations and other operationsdescribed herein. The IC may perform some operations based on executionof programming instructions read from the ROM or the RAM, with otheroperations hardwired into gates or other logic. Further, an IC may beconfigured to output image data to a display buffer.

Services provided by the local office 103 and/or the service provider118 (e.g., using the server 120 at the service provider 118 and/or aserver located at a remote location) may comprise network digital videorecording services. Those services may be implemented using hardwarecomponents or a combination of hardware and software components deployedas an integrated, fault-tolerant computing platform. In a systemexperiencing no connectivity or system failures, for a given recordingfor a given user, a single copy may be made. However, where a singlenDVR fails or experiences reduced capacity, one or more nDVRs in otherlocations (e.g., other data centers, other local offices, other serviceproviders, etc.) may assist in the recording workload. For purposes ofexplanation, “data center” may be used to refer generally to a localoffice, a service provider, and/or other collection of computingdevices. Different data centers may cooperate and share their nDVRsamong themselves. If an nDVR of a first of those data centers may beoffline, an nDVR of another of those data centers may make recordingdecisions by itself. Further, based on the offline nDVR coming backonline, the overall system may recover by consolidating recordedsegments and/or de-duplicating duplicate recordings of the same segment(if any) for a single user. Further, having at least one partiallyredundant system may permit opportunities for system maintenance withouttemporary loss of recording capabilities.

Independent nDVRs may be located in different data centers. A ratio ofsegments recorded between associated data centers may be equal (e.g.,50% of recording requests initially received by one data center beingsent to another data center) or may be biased (e.g., 80% of recordingsrequests initially received by one data center may be handled locallywhile the remaining 20% may be handled by one or more other datacenters). FIG. 3 shows an example of an arrangement of two nDVRs, eachin a separate data center. FIG. 4 shows an example of an arrangement ofthree nDVRs, each in a separate data center.

FIG. 3 shows an example of two nDVRs in separate data centers that mayassist each other if one of the two nDVRs is unable to service all ofits recording requests. FIG. 3 shows a first nDVR 301, a second nDVR302, and a device 303 (e.g., a user device). The device 303 may send oneor more messages indicating content item that a user desires to record.The first nDVR 301 may be located in a data center 321 and the secondnDVR 302 may be located in a data center 322. The data centers 321 and322 may be geographically separated from each other and primarily servethe customers in their respective regions. The regions may be generallyshown as above and below dashed line 323.

Content such as video programs may be received from a content provider304, with the content provider 304 having various storage devices andservers (not shown). Content items to be recorded may be indicatedthrough messages from a guide scheduling server 1607 (described inrelation to FIG. 16 below). The content items may comprise a pluralityof segments storable on a storage medium.

If more recording requests exist than a single nDVR may be able tohandle, the nDVR may not be able to satisfy all recording requests. ThenDVR 301 in the data center 321 may comprise a capacity exchange server309 that may exchange capacity information with another capacityexchange server 315 of another nDVR 302 in a different data center 322.The data centers may be connected by a high capacity network link 317(for example, 80 Gbps or above).

A device 303 (e.g., one or more devices 112-117 of the premises 102 a,or another computing device) may be in communication with the first nDVR301 via a network as described in FIGS. 1 and 2. The device 303 may beone or more of the devices described in FIG. 1 including but not limitedto set-top boxes (STBs), digital video recorders (DVRs), computerservers, televisions, personal computers, laptop computers, wirelessdevices (comprising wireless laptops and netbooks, mobile phones, mobiletelevisions, personal digital assistants (PDA), etc.), and/or any othercomputing device. The device 303 may send one or more requests forrecording of content to the first nDVR 301. In FIG. 3, the contentrequested to be recorded may be provided by a content provider 304. InFIG. 3, the content provider 304 may be connected to both the first nDVR301 and the second nDVR 302. The connection may comprise one of theconnection networks described in FIG. 1.

To retrieve a content item to be recorded, the nDVR 301 may send arequest to the content provider 304 to obtain one or more segments ofthe content item. The request may be a hypertext transfer protocol(HTTP) GET command, an HTTP POST command, or other request. In the firstnDVR 301, one or more channel monitor servers 305 may read one or morelists of segments to be recorded. The one or more channel monitorservers 305 may distribute the recording requests among one or moremedia recorder servers 306. The lists of segments may comprise adaptivebitrate manifests comprising one or more of video, audio, pixelresolution, and related information for the segments (e.g., the lengthof each segment). The content item may arrive in two-second segments.The lists of segments to record may also indicate the origin of thecontent item.

The first nDVR 301 may comprise one or more channel monitor servers 305that may monitor channels for the content to be recorded. Each of themultiple channel monitor servers 305 may monitor a specific logicalservice (e.g., NBC, ESPN, HBO, and the like) (referred to herein as a“channel”) or may monitor multiple logical services (or channels). Eachchannel may have a designated primary recording location selected fromone of the data center 321 and the data center 322. The other of thedata center 321 and the data center 322 may be designated as thesecondary recording location. If the primary recording location for achannel is unavailable or overloaded, the secondary recording locationof the data centers 301 and 302 may temporarily handle any recording,archiving, and/or reconstitution processes for the primary recordinglocation while the primary recording location is unavailable. In FIG. 3with the two data centers 321 and 322, any data center not designated asthe primary recording location for a specific channel may be thesecondary recording location for that channel. In FIG. 4 with three datacenters 431-433, a data center not designated as the primary recordinglocation for that channel may be either a secondary or tertiaryrecording location for that channel. With three or more data centersthat work together to service users, additional ordered designations maybe made (quaternary, quinary, senary, and the like). A tertiary and/orother higher order designation may be optional. For example, three ormore data centers may be associated to serve a region of users but onlya secondary recording location designated and no tertiary or subsequentpriority of recording locations designated. Reducing the quantity oftertiary and subsequent recording locations may provide reduced overheadcomputing as a tradeoff for reduced backup capabilities in rare times ofmultiple data centers being overloaded or unavailable.

Information indicating the content, the channel, the user (and/or theuser's account and/or the user's device) for which the segment may berecorded, and other relevant information may be sent to one or more ofthe channel monitor servers 305 and/or one or more of the media recorderservers 306. The channel monitor servers 305 (referred to herein as“channel monitors”) may monitor specific channels for the contentindicated by users by reading adaptive bit rate manifests from thecontent provider 304. The content from the content provider 304 may bereceived as adaptive bitrate manifests identifying and/or indicatingsegments of a given length (e.g., from 2-6 seconds). The channelmonitors 305 may read indication information from the adaptive bitratemanifests and check whether content items requested by one or more ofthe users appears in the adaptive bitrate manifests. Based on a segmenthaving been identified by a channel monitor, the channel monitor mayrequest one or more of the media recorder servers 306 (referred toherein as “media recorders”) to record the identified segment andpossibly the quantity of copies of the segment to be recorded. The mediarecorder servers 306 may record the incoming segments in the mediastorage 308. The media recorder servers 306 may generate metadataindexes 307 that indicate the recorded segments in the media storage 308for subsequent retrieval, archiving, and/or reconstitution. An internalnetwork 310 may interconnect the various components of the nDVR 301. Amedia recorder server 306 may perform a single access of the segmentfrom the storage medium and may generate a copy of the segment in themedia storage 308 for each request received by the nDVR 301 to recordthe content item. The adaptive bitrate manifests may also be distributedby the content provider 304 to the nDVR 302 in the data center 322,permitting the nDVR 302 to record segments if the nDVR 301 or the datacenter 321 may be offline and/or may otherwise not be recording thesegments in which the nDVR 301 was indicated as the primary recordinglocation.

The second nDVR 302 in the data center 322 may comprise similarcomponents to those of the first nDVR 301 in the data center 321. Thesecond nDVR 302 may comprise one or more channel monitors 311 thatmonitor different channels for the content to be recorded. The secondnDVR 302 may also receive content from the content provider 304. Thechannel monitors 311 may detect segments to be recorded and may instructone or more media recorders 312 to record the detected segments. Themedia recorders 312 may record the incoming segments in the mediastorage 314. The media recorders 312 may generate metadata indexes 313that specify the recorded segments for subsequent retrieval, archiving,and/or reconstitution. To further assist the detection of segments andthe recording of detected segments, the second nDVR 302 may receiverecording requests from the device 303 and may assist in the recordingof the detected segments.

The first nDVR 301 may further comprise a capacity exchange server 309that may exchange capacity information with a capacity exchange server315 of the second nDVR 302 via a communication link 317. Thecommunication link 317 may include a high capacity fiber opticpoint-to-point connection, a high capacity fiber optic network, and/orother connection. The exchanged capacity information may permit thesecond nDVR 302 of the data center 322 to assist the first nDVR 301 ofthe data center 321 in the recording of content where that content maynormally be recorded by the first nDVR 301 of the data center 321.Likewise, the first nDVR 301 may assist the second nDVR 302 by recordingcontent that may normally be recorded by the second nDVR 302. Further,heartbeat signals may be exchanged between the capacity servers 309 and315. The failure of a first capacity exchange server to receive theheartbeat from a second capacity exchange server within an expected timewindow may be interpreted by the first capacity exchange server asindicative that the nDVR associated with the second capacity exchangeserver may be unavailable.

A collection of the capacity exchange servers may treat each nDVR as asingle system as having at least two general statuses: availablecapacity and diminished capacity (where diminished capacity includes nocapacity, e.g., being partitioned). These two general statuses may besubdivided into additional statuses as desired. Where a given nDVR mayhave diminished capacity relative to being able to satisfy the recordingrequests from user devices of which it may be associated, the channelmonitor servers may designate another nDVR as the primary recordinglocation. That other nDVR may have the most available capacity and/orthe best redundancy. A 1080-pixel video track may be recorded on onenDVR with higher available capacity and a 720-pixel track may berecorded on a different nDVR with lower capacity or the tracks may berecorded by the same nDVR.

FIG. 4 shows an example of three nDVRs exchanging capacity informationand assisting each other in the recording of content. User devices andcontent providers are not shown in FIG. 4. FIG. 4 shows an nDVR 401 in adata center 431, an nDVR 402 in a data center 432, and an nDVR 403 in adata center 433. The data centers 431-433 may be geographicallyseparated from each other as shown generally by dashed lines 434 or maybe located together but designated to serve different groups of users.

The nDVRs 401-403 may include similar components to those of the nDVRs301 and 302 of FIG. 3. Specifically, the nDVR 401 may comprise one ormore channel monitoring servers 404, one or more media recorder servers405, metadata indexes 406, media storage 407, and a capacity exchangeserver 408, with these components connected by an internal network 409.The nDVR 402 may comprise one or more channel monitoring servers 409,one or more media recorder servers 410, metadata indexes 411, mediastorage 412, and a capacity exchange server 413, with these componentsconnected by an internal network 414. The nDVR 403 may comprise one ormore channel monitoring servers 415, one or more media recorder servers416, metadata indexes 417, media storage 418, and a capacity exchangeserver 419, with these components connected by an internal network 420.The nDVR 401 may be connected to the nDVR 402 via a high speedconnection 421, the nDVR 402 may be connected to the nDVR 403 via a highspeed connection 422, and the nDVR 403 may be connected to the nDVR 401via a high speed connection 423. The high speed connections 421-423 maybe three separate connections or may be part of a single networkinterconnecting nDVRs 401-403 and the data centers in which they arelocated. The capacity exchange server 408 may exchange capacityinformation with each of the capacity exchange server 413 and thecapacity exchange server 419.

One copy of a recorded content item may ultimately exist, across acollection of nDVRs, per requesting user. A copy of a segment may beused to fill in missing segments of other recordings based on networkfailures or connectivity issues. For example, the first nDVR 301 may be,at times, unable to record all segments of requested content. Thisunavailability may be due to a spike in requests from devices thatcauses the recording capacity for the first nDVR 301 to be exceeded. Thefirst nDVR 301 may suffer a component failure or network failure thatreduces its recording capacity for an interval long enough to reduce itsability to record segments. Further, the capacity exchange between thefirst nDVR 301 and the second nDVR 302 may be disrupted such that thesecond nDVR 302 may not know whether the first nDVR 301 may be capableof, or is in fact, recording segments. The first nDVR 301 may not beexchanging heartbeat signals with the second nDVR 302.

Based on the lack of a heartbeat from a capacity exchange server of oneof the nDVRs, the remaining nDVRs may begin recording segments based ontheir own determinations of where segments should be recorded based oneach's determination of which segments should be recorded locally inview of the altered recording capacity across the data centers. Thecapacity exchange servers of the nDVRs may permit each of the connectednDVRs to know the current capacity of the other nDVRs and to handlefaults and sudden spikes gracefully by dynamically adjusting theirrecordings in light of changes in capacity of the other nDVRs.

Each capacity exchange server may receive one or more capacity reportsfrom the other capacity exchange servers. A capacity report may includecurrent usage and/or maximum capabilities for one or more of thefollowing: a disk writing load, a disk reading load, a disk networkload, or a computational network load.

FIG. 5A is a flowchart showing an example method 500 for exchangingcapacity data using the capacity exchange servers. Although FIG. 5A andother figures describe operations performed by capacity exchange serversand/or by other elements, some or all operations may also oralternatively be performed by one or more computing devices. In step501, an nDVR's capacity exchange server may receive capacity informationfrom other components in the nDVR (e.g., one or more of the channelmonitors, the media recorders, and/or media storage). The capacityexchange server may poll each of the channel monitors, media recorders,and/or media storage or may wait for one or more of these elements toforward its status to the capacity exchange server. The capacityexchange server may assemble the received capacity information into asummary of capacity for that local nDVR. In step 502, the capacityexchange server may forward the current local capacity data to acapacity exchange server at a remote nDVR (e.g., where only two nDVRs ofdifferent data centers are grouped together as shown in FIG. 3) or mayforward the current local capacity data to two or more capacity exchangeservers (e.g., where three nDVRs of different data centers are groupedtogether as shown in FIG. 4). The capacity exchange server may forwardthe current local capacity data to as many other capacity exchangeservers as are present in the group of nDVRs.

In step 503, the capacity exchange server may receive current remotecapacity data from the one or more other capacity exchange servers. Instep 504, the local capacity exchange server may combine current localcapacity data with the current remote capacity data to generate asnapshot of the current network capacity. That snapshot may be madeavailable to computing devices associated with the capacity exchangeserver (e.g., the channel monitors 305 and 404) as current networkcapacity data. The current network capacity data may be sent to thelocal computing devices reflecting updates. The current network capacitydata may be sent in response to a request for the current networkcapacity data from those local computing devices. In step 504, thecurrent capacity data may be made available to one or more computingdevices of the local location. The computing devices may include thechannel monitors, the media recorders, storage devices, and processorsthat consolidate and de-duplicate duplicate recordings, and the like.

In step 505, the local capacity exchange server may wait until the endof a heartbeat duration interval. The local capacity exchange server mayagain receive capacity information from other components in the nDVR instep 501. The heartbeat interval may be two seconds, six seconds, orother interval(s) shorter or longer than two seconds or six seconds. Theheartbeat duration interval may reflect one or more time windowsassociated with one or more timers during which heartbeat signals fromother capacity exchange servers are expected to be received.

FIG. 5B is a flowchart showing an example method 510 of combining statusinformation into a local capacity/heartbeat message. A capacity exchangeserver may obtain local status information from channel monitors, mediarecorders, and/or media storage. The capacity exchange server may pollmedia recorders, storage devices, and/or servers for status information,and/or those devices may store their statuses in a local memory and thecapacity exchange server may read the statutes from that local memory.In step 511, the capacity exchange server may obtain a location ID. Thecapacity exchange server may obtain statuses comprising one or more ofcurrent disk read activity (step 512), current disk write activity (step513), current disk network activity (step 514), or current computational(processing load) activity (step 515). The capacity exchange server mayalso obtain a maximum capability for each nDVR comprising one or more ofa maximum disk read activity, a maximum disk write activity, a maximumdisk network activity, or a maximum computational (processing load)activity. The maximum capability may be obtained in the above steps512-515 or may be obtained during a separate process. In step 516, thecollected information may be combined by the capacity server into alocal capacity/heartbeat message.

The local capacity/heartbeat message may be interpreted by remotecapacity exchange servers as one or more of an indication of the localcapacity of the nDVR to which the local capacity exchange server belongsand/or a heartbeat from the local capacity exchange server. Based on thelocal capacity/heartbeat message not being received by the remotecapacity exchange servers within a predetermined period of time (e.g., 2seconds), the remote capacity exchange servers may interpret the maximumcapacities of the local nDVR to be zero (e.g., having no capacity).

The local capacity/heartbeat message may be part of or separate fromother heartbeat messages between the capacity exchange servers. Thelocal capacity/heartbeat message with the local capacity information maybe sent on one timing interval (e.g., 4-6 seconds), while separateheartbeat messages may be sent on another timing interval (e.g., 2-3seconds). The local capacity/heartbeat message may operate as aheartbeat message with separate interstitial (more frequent) heartbeatmessages transmitted by the local capacity exchange server to the remotecapacity exchange servers.

With respect to the heartbeat, one or more timers may be accessible byeach capacity exchange server, one for each of the other capacityexchange servers. Based on receiving a heartbeat signal of one of theother capacity exchange servers, the timer associated with that capacityexchange server may be reset. The failure to receive a heartbeat fromthe other capacity exchange server before the expiration of the timerfor that other capacity exchange server may be interpreted as the nDVRassociated with the non-responsive capacity exchange server has nocapacity to fulfill its recording tasks. The remaining nDVRs maydetermine whether they have the highest scoring location accounting forthe reduced capacity of the network having temporarily lost connectionwith an nDVR.

The local capacity/heartbeat message may comprise an HTTP POST messagewith payload or other messaging techniques. The following showsnon-limiting examples of content of such a capacity exchange/heartbeatmessage in pseudo-code:

POST /capacity { “kind” : “Heartbeat”, “time” : “2015-08-22T13:57:24Z”,“Location” : “cdvr-x-rmID-abrn01”, “DiskRead” : { “Now” : 0, “Max” :8000000 }, “DiskWrite” : { “Now” : 0, “Max” : 8000000 }, “DiskNetwork” :{ “Now” : 0, “Max” : 16000000 }, “ComputeNetwork” : { “Now” : 0, “Max” :16000000 } }

The capacity heartbeat message shown above is an HTTP Post commandindicating itself in the header to be a capacity-related message. Thecapacity heartbeat message may indicate itself to be a “heartbeat”message with the “kind” attribute. The time of generation may beincluded with the “time” attribute. The location or name of the nDVR maybe referenced with the “location” attribute. A current playback status(“Now”) and maximum playback capacity (“Max”) may be provided with the“DiskRead” attribute. A current recording status (“Now”) and maximumrecording capacity (“Max”) may be provided with the “DiskWrite”attribute. A current internal network load (“Now”) and maximum capacity(“Max”) may be provided with the “DiskNetwork” attribute. A currentprocessor load (“Now”) and maximum capacity (“Max”) may be provided withthe “ComputeNetwork” attribute. Values for the “Now” and “Max”parameters the “DiskRead” attribute, “DiskWrite” attribute,“DiskNetwork” attribute, and/or “ComputeNetwork” attribute may be insegments per unit of time.

The exchange of capacity information may be a heartbeat signal such asshown with respect to the pseudocode above. Additionally oralternatively, heartbeat information may be provided separately fromcapacity information. In slowly varying systems or in systems withsignificant capacity, capacity updates may not be needed as oftencompared to either quickly varying systems or to systems with reducedcapacity. Accordingly, heartbeat signals may be provided independentfrom or in addition to less frequent capacity exchanges.

FIG. 6 is a flowchart showing an example of a method by which a localnDVR may determine which segments to record. The flowchart of FIG. 6 isdescribed in relation to the environment of FIG. 3 but may equally beapplied to the environment of FIG. 4 and environments having more datacenters. With respect to FIG. 3, the device 303 may request recording of“The Walking Dead” when that content item next appears on the AMCchannel. The request may be provided to a specific channel monitor 305that monitors the AMC channel for the content to be recorded. Thecontent may be provided by a channel server. The specific channelmonitor 305 may receive the designation of what to record from one ormore servers along with an indication of how many copies of the contentshould be recorded. The one or more servers providing the indication ofhow many copies to record may comprise one or more guide schedulingservers (e.g., the guide scheduling server 1607 of FIG. 16). The channelmonitor 305 monitoring the AMC channel may read a channel manifest fromthe AMC channel server. The channel manifest from the AMC channel servermay be the current content available on the AMC channel during apredetermined interval (e.g., during a 2 second interval). Further, thechannel manifest may indicate a single resolution version (e.g., 1080p)of the content or may indicate multiple resolution versions of thecontent (e.g., one or more of 288p, 360p, 432p, 720p, or 1080p).

In step 601 of FIG. 6, the channel monitor may read a most recentchannel manifest from a channel server. The channel monitor may readfrom the channel manifest that “The Walking Dead” is playing for thenext 2 seconds at 5 separate resolutions. In step 603, the channelmonitor may determine the list of segments to be recorded (e.g., 5separate segments). Comparing a channel manifest with the list ofcontent to be recorded, the channel monitor (in step 603) may determinethe list of segments to be recorded. The AMC channel monitor may comparea list of segments to be recorded to the current channel manifest fromAMC and may detect a match with a current segment of “The Walking Dead”.In step 604, the channel monitor may read a local location media index.The local location media index may specify the quantity of copies to berecorded for the specific content (e.g., the local location media indexmay indicate that 205 copies of the content should be recorded). Thequantity of copies of segments to be recorded may be the same as thequantity of requests for the content as related to a default resolution(e.g., 1080p). The quantity of copies of segments to be recorded mayindicate the recording of two or more resolutions of the content peruser request to permit playback on different devices in the nativeresolution of each device. For example, if 205 users requested recordingof “The Walking Dead” and five resolutions are offered in the channelmanifest, 1025 segments may be indicated to be recorded.

In step 606, the channel monitor may read current network capacity data(e.g., capacity data for multiple nDVRs) from the local capacityexchange server. The following pseudocode shows an example format for arequest of capacity (the “GET/capacity” command) and an example of aresponse providing the current data (e.g., the response content betweenthe outer curly braces) reflecting an aggregated capacity report ofmultiple nDVRs:

GET Command: GET /capacity Response: { “kind” : “Capacity”, “time” :“2015-08-22T13:57:24Z”, “Locations” : [ { “Location” :“cdvr-x-rmID-mana01”, “DiskRead” : { “Now” : 0, “Max” : 1000000 },“DiskWrite” : { “Now” : 0, “Max” : 1000000 }, “DiskNetwork” : { “Now” :0, “Max” : 16000000 }, “ComputeNetwork” : { “Now” : 0, “Max” : 16000000} }, { “Location” : “cdvr-x-rmID-abrn01”, “DiskRead” : { “Now” : 0,“Max” : 8000000 }, “DiskWrite” : { “Now” : 0, “Max” : 8000000 },“DiskNetwork” : { “Now” : 0, “Max” : 16000000 }, “ComputeNetwork” : {“Now” : 0, “Max” : 16000000 } } ] }

The aggregate capacity report may be based on an HTTP Get command wherethe information being retrieved relates to capacity. The “kind”attribute may indicate that the response relates to the aggregatecapacity of the system. The “time” attribute may indicate the time atwhich the report was generated. The “Locations” section of the reportmay relate to indicating the capacity of the specific locations of thecapacity exchange servers. For each of the locations indicated, the nameof the location may be provided with the “Location” attribute. A currentplayback load (“Now”) and a maximum capacity (“Max”) at that specificlocation may be provided with the “DiskRead” attribute. A currentrecording load (“Now”) and a maximum capacity (“Max”) at that specificlocation may be provided with the “DiskWrite” attribute. A currentinternal network load (“Now”) and a maximum capacity (“Max”) for thelocation may be provided with the “DiskNetwork” attribute. A currentprocessor load (“Now”) and a maximum capacity (“Max”) for the locationmay be provided with the “ComputeNetwork” attribute. Values for the“Now” and “Max” parameters the “DiskRead” attribute, “DiskWrite”attribute, “DiskNetwork” attribute, and/or “ComputeNetwork” attributemay be in segments per unit of time, groups of segments per unit oftime, and/or other units.

The capacity for connected nDVRs may be represented by C. The capacityfor each by c for each nDVR j may be represented by c. The capacity Cacross the network may be represented by the following equation:C=Σ ₀ ^(j) c _(j)  (1)

where C is the sum of the capacities c of individual nDVRs 0-j.

In step 608, the channel monitor may determine, for each segment to berecorded, the highest scoring nDVR j for that segment to be recorded.The scoring may be based on the aggregate capacity report or acombination of the aggregate capacity report and the sum C ofcapacities.

The determination of the highest scoring nDVR j for a segment may beperformed irrespective of the resolution of the segment. Additionally oralternatively, each resolution of the segment may be used in the scoringof each segment (e.g., a first nDVR may be a preferred recordinglocation for a first resolution of the segment while a second nDVR maybe a preferred recording location for a second resolution of thesegment). Additionally or alternatively, one or more of the differentresolutions of the segments may be recorded at a common recordinglocation.

The channel monitor (e.g. a channel monitor server 305) may output alist of individual segments and local media recorder server(s) (e.g. oneor more of media recorder servers 306) to record the segments. In step610, the designated local media recorder servers may record thesegments. In step 611, the channel monitor may wait until the channelmanifest is refreshed and may read the next channel manifest in step601.

The scoring performed by the channel monitor in step 608 may beperformed locally in each channel monitor in each nDVR based oninformation distributed to each nDVR, the information comprising thechannel manifest, the local location media index, and the currentnetwork capacity data. By permitting one or more nDVRs to determine thehighest scoring location j for each segment to be recorded across thenetwork of data centers, the robustness of the recording ability of thecombination of nDVRs working across the data centers may be enhanced. Inan environment in which all nDVRs may be sharing capacity data, eachnDVR may be determining the same highest scoring location per segment.However, in an environment where one of the nDVRs may be partitionedfrom two or more other nDVRs, the first nDVR may attempt to compensatefor the zero capacity (from its perspective) other nDVRs. Likewise, theother two nDVRs may attempt to compensate for the zero capacity (fromtheir perspective) of the first nDVR. Additionally or alternatively, thescoring may be performed in other channel monitors and the informationshared among the channel monitors.

Additional location information may be included in the heuristics ofstep 608 to prioritize, for a determination of where to record asegment, one nDVR over other nDVR(s). Additionally or alternatively, theadditional location information may be included to prioritize, fordetermination of archiving and/or subsequent reconstitution of segments,one nDVR over other nDVR(s).

FIGS. 7A-7C show information that may be used in determining at whichlocation segments should be recorded, archived, and/or reconstituted.Various types of information are shown in FIGS. 7A-7C for scoring thenDVRs in different data centers. These information sets are examples.Information in these information sets may be replaced with otherinformation and/or augmented with other information.

FIG. 7A shows information 701 comprising a preferred location 704 wherecontent for a given channel may be recorded. The preferred location 704may be general to all resolutions for a channel or may be specific toparticular resolutions for that channel. In systems with only two nDVRs,only a primary location may be indicated or both the primary locationand the secondary location may be indicated. In systems with three ormore nDVRs, a primary location and a secondary location (and possibly atertiary location and/or others) may be indicated to provide an orderedlist of locations in case one or more of the locations may beunavailable. The closest server to a user or a group of users may beprovided as information 705. The users may be grouped to help reduceoverhead calculations by indicating locations for all users who aremembers of a group. For example, users 1-500 who record content from theAMC channel may have their closest nDVR be different than users 501-1000who also record content from the AMC channel. The quantity of users pergroup may be variable and may be readily increased or decreased per thecapacity of the network.

The least loaded nDVR may be indicated in information 706. Information706 may comprise disk writes capacity, disk network capacity, and/orcompute network capacity. Disk read capacity may be of less importanceduring recording. The location where the previous segment was recordedmay be indicated in information 707.

FIG. 7B shows information 702 that may be considered in determiningwhere segments should be archived. Information 708 may comprise anindication of a designated archive location (general per channel and/orspecific for channel/resolution). Information 709 may indicate theclosest server to a user or a group of users. The least loaded nDVR maybe indicated in information 710. The location where the previous segmentwas recorded may be indicated in information 711.

FIG. 7C shows information 703 that may be considered in determiningwhere segments should be reconstituted. Information 712 may comprise anindication of the archived location of the segment. Information 713 mayindicate the closest server to a user or a group of users. The leastloaded nDVR may be indicated in information 714. Other information(including possible biasing for expected future network loads) may beindicated in information 715.

FIG. 8 shows an example of a general timeline of archiving andreconstituting segments. For days 0-3 after recording, the recordingsmay be played back from an active server. After day 3, the content maybe archived and subsequently reconstituted on days 3+ for playback froman active server. Time intervals longer or shorter than 3 days may beused to determine when recordings should be archived.

FIG. 9 shows an example of a channel manifest 901 for a channel X withsegments of content Y, having resolution P1 and P2, for times t0-t9. Alocal location media index 902 may indicate the content requested byspecific users. In FIG. 9, three users of two different groups of usershave requested content Y (e.g., a user 1 of a Group G, a user 2 of theGroup G, and a user 3 of a Group H).

Capacity information for an nDVR A 903 and capacity information for annDVR B 904 may be gathered, may be exchanged between the nDVR A'scapacity exchange server and nDVR B's capacity exchange server, and maybe stored by each nDVR's capacity exchange server. The capacityinformation for each nDVR may comprise current usage and maximum usagecapabilities for one or more of the following: disk reads (DR), diskwrites (DW), disk network load (DN), or computational network load (CN).Information 906 may indicate the designated recording location perchannel/resolution. Information 906 may be provided, for a given nDVR,from the nDVR's capacity exchange server to the nDVR's channel monitor.Information 907 may indicate the closest nDVR per user or group ofusers. Information 907 may be provided, for the given nDVR, from thenDVR's capacity exchange server to the nDVR's the channel monitor.

Based on one or more of the channel manifest 901, the local locationmedia index 902, the capacities of nDVRs A (903) and B (904), thedesignated recording location per channel/resolution 906, or the closestnDVR per a user or group of users 907, the given nDVR's channel monitormay score the locations for recording the particular segments in a table905. The results of table 905 may be sent to the given nDVR's mediarecorder server as a segment/location list of FIG. 6.

FIG. 10 shows an example of weighted, additive scoring that may be usedin conjunction with step 606 of FIG. 6. Other scoring processes may beused in addition to or in place of that shown in FIG. 10. FIG. 10 showsa list of segments 1001 at resolutions P1/P2 at times t0-t9 on channel Xfor the users 1 and 2 of the Group G and the user 3 of the Group H. ThenDVR location indicated for recording the channel per resolution may beindicated in the column 1002. The nDVR closest to the user/group may beindicated in the column 1003. The least loaded nDVR may be indicated inthe column 1004. The location where previous segment was recorded may beindicated in the column 1005. The weighting factors that have beenapplied in this example comprise 0.5, 0.5, 2.0, and 1.1, respectively.These weighting factors are indicated for explanatory purposes only andmay be varied to adjust the scorings to alter the distributions ofresulting locations as needed. The sums of weighted values for the nDVRA may be indicated in the column 1006 and the sum of weighted values forthe nDVR B may be indicated in the column 1007. The recording locationfor each of the segments 1001 may be the recording location with thehigher score of column 1006 and column 1007. The recording location withthe higher score may be represented in the column 1008.

In FIG. 10, the nDVR A may be designated as the primary recordinglocation of segments with resolution P1 while the nDVR B may bedesignated as the primary recording location of segments with resolutionP2. The least loaded nDVR may initially be the nDVR A, may shift to thenDVR B for time t1, and may return to the nDVR A for time t9. Theprimary weighting factor in FIG. 10 may be the least loaded nDVRindicated in the column 1004. For t1, despite the previous recordings ofthe segment having been recorded by nDVR A, the segment P2 for the User2/Group G and the segment P1 for the User 3/Group H may be recorded bythe nDVR B based on the combination of the nDVR B being least loaded andone of the location indicated for recording (the column 1002) and theclosest nDVR (the column 1003) being the nDVR B. The score for theremaining segments are all indicating the nDVR A as the recordinglocation.

The weighting factors of each of the values may be constant or may varyover time. The weighting factors may be based on events happening in thecurrent network. The weighting factors may be varied to bias a recordingcapacity for a given nDVR ahead of an anticipated capacity shift basedon historical capacity information. Additionally or alternatively, theheuristics may be tied to user content selections (e.g., recordingcontent from a sporting event that does not occur on a short window (forexample, weekly, bi-weekly, semi-monthly, monthly, and the like)basis—such as the Olympics held in another time zone). Capacityinformation may be biased ahead of time to limit the expected recordingcapability, thereby providing less capacity to other capacity exchangeservers and providing more capacity for the local nDVR during expectedspikes in upcoming recording requests.

A state of a first nDVR being off-line or no longer communicating withother nDVRs may be referred to as being “partitioned” from the othernDVRs. While the first nDVR may be under partition (not able to send itsheartbeat signal to other nDVRs), the remaining nDVRs may compensate forthe unavailable nDVR by recording specific segments originallydetermined to be recorded by the first (now unavailable) nDVR. Based onthe first nDVR being available again, the segments recorded by othernDVRs may be consolidated and stored in a storage device of the firstnDVR. Duplicate recordings of segments for the same user may be removedat a later time.

Archiving, reconstitution, and/or playback systems may also use thecapacity exchange servers to determine the location with the bestcapacity to archive, reconstitute, and/or play back recorded content.Each of these systems may implement its own load balancing heuristicusing capacity data from its local capacity exchange server.

A single nDVR under partition may function (if, in fact, functioning) asit would without a capacity exchange server in that only local statusinformation is considered for recording, playback, archiving, and/orreconstitution. Until the partition is removed (e.g., a connection isrestored between the affected nDVR and one or more additional nDVRs),specific media files originally intended to be recorded on a local nDVRbut recorded elsewhere may not be able to be played. Based on the nDVRno longer being partitioned, the recorded content may be moved from theother nDVR to the local nDVR for archiving and/or playback.

Recovery from a partition may be achieved by replicating the metadataindexes indicating where the recorded content may be stored until themetadata indexes agree. Playback may initiate from either system, withthe media fragment retrievals coming from the system where the media mayreside and being consolidated and/or archived at a designated nDVR.

If a partitioned nDVR was active under partition, identical segments mayhave been recorded by the partitioned nDVR and another nDVR. If one copyof each recording per requesting user is desired, the various segmentsmay be consolidated into the single recording per requesting user. Basedon connectivity or capability being restored, the nDVRs may exchangemetadata indexes and use the exchanged metadata indexes to de-duplicaterecorded segments to result in a single copy of content per requestinguser.

Each capacity exchange server may treat its own one or more channelmonitor servers, one or more media recorders, metadata indexes, andmedia storage as a single entity for reporting capacity information tothe other capacity exchange servers. Each capacity exchange server maytreat each of these components separately and/or report them separately.Subgroups of components may be consolidated to reduce the reportingoverhead for each capacity exchange server. Based on a given capacityexchange server determining that its own media storage is offline, itmay report that its nDVR has low or no maximum disk read or disk writecapacity. Additionally or alternatively, the capacity exchange servermay not forward a heartbeat signal, thereby forcing the other capacityexchange servers to determine that the nDVR (to which the given capacityexchange server belongs) may likely be offline.

With respect to consolidating recordings, there may be a benefit ofkeeping recordings for a given channel in one data center. Organizingthe recordings by channel in one data center (e.g., a primary locationfor the content from each channel) may make deduplication easier by nothaving to send the content between data centers but only move thecontent locally (if at all) to consolidate the recorded segments.

FIG. 11 is flowchart showing a method for determining where to archiverecorded segments and/or where to reconstitute archived segments. At day3 (or other time period after recording), segments may be archived.Another measure of time may be used including but not limited toseconds, minutes, hours, weeks, months, and the like and fractionsthereof. Based on a request for playback from a user, the archivedsegments may be reconstituted at an active server for playback. In step1101, the nDVRs may share metadata indexes to determine the locations ofrecorded segments and the existence of duplicate recorded segments. Thelist of segments to be archived or reconstituted may be generated andmay be distributed among the nDVRs. Additionally or alternatively, aseach nDVR exchanges the metadata indexes, each may generate its own copyof the lists of segments to be archived or reconstituted.

In step 1103, the local nDVR may read the list of the segments to bearchived or reconstituted. In step 1104, the local nDVR may readcapacity data from its capacity exchange server that stores the capacitydata from across the network. In step 1106, for each segment to bearchived or reconstituted, the local nDVR may determine the highestscoring location for that segment and may store that value in an archivelocation list. Because the nDVRs may all be performing step 1106locally, they may each determine the highest scoring location for thatsegment. Where an nDVR determines itself to be the highest scoringlocation for that segment, the segment may be archived or reconstitutedby that nDVR (step 1108). This may comprise sending segments stored in adifferent nDVR to the indicated nDVR as well as deleting duplicaterecordings of segments. Some segments for the user of the same contentmay have been recorded at multiple locations based on one nDVR appearedto be offline or suffering from reduced capacity.

FIG. 12 shows examples of information that may be used to determinewhere to archive the segments of FIG. 11 across nDVRs. A metadata index1201 for an nDVR A of recorded segments may be combined with a metadataindex 1202 for an nDVR B to generate a list 1205 indicating the recordedsegments and where they are currently located.

Current capacity information 1203 of the nDVR A and current capacityinformation 1204 of the nDVR B may be exchanged via respective capacityexchange servers. The designated archive location per channel/resolutionmay be provided as information 1206. Information indicating the closestnDVR per user/group may be provided as data 1207. The scores of rankingsfor where to store the segments may be determined and the results may bepopulated into the list 1205.

The segment Q1 for time t2 for the User 1/Group G may have been recordedby both the nDVR A and the nDVR B. Based on the determination that thesegment is to be archived by the nDVR A, the copy on the nDVR B may beindicated as to be deleted.

FIG. 13 shows an example of weighted, additive scoring that may be usedin conjunction with step 1106 of FIG. 11. Other scoring processes may beused in addition to or in place of that shown in FIG. 13. FIG. 13 showsa list of segments 1301 at resolutions Q1/Q2 at times t0-t2 on a channelY for the users 1 and 2 of the Group G and the user 3 of the Group H.The nDVR location indicated for archiving the channel per resolution maybe indicated in the column 1302. The nDVR closest to the user/group maybe indicated in the column 1303. The least loaded nDVR may be indicatedin the column 1304. The previous segment's recorded location may beindicated in the column 1305. The weighting factors that applied in thisexample are 1.5, 0.5, 0.5, and 0.1, respectively. These weightingfactors are indicated for explanatory purposes only and may be varied toadjust the scorings to alter the distributions of resulting locations asneeded. The sums of weighted values for the nDVR A may be indicated inthe column 1306 and the sum of weighted values for the nDVR B may beindicated in the column 1307. The archiving location for each of thesegments 1301 may be the archiving location with the higher score ofcolumn 1306 and column 1307. The archiving location with the higherscore may be represented in the column 1308.

In FIG. 13, an nDVR A may be designated as the primary archivinglocation of segments Q1 while an nDVR B may be designated as the primaryarchiving location of segments Q2. The least loaded nDVR may initiallybe the nDVR A, may shift to the nDVR B for time t1, and may return tothe nDVR A for time t2. The primary weighting factor in FIG. 13 may bethe designated archive location of the column 1302. The archiving of thesegments may follow that designated archive location.

FIG. 14 shows examples of information that may be used to determinewhere to reconstitute content across nDVRs. A metadata index 1401 for annDVR A of recorded segments may be combined with a metadata index 1402for an nDVR B to generate a list 1405 indicating the archived segmentsand where they are currently archived.

Current capacity information 1403 of the nDVR A and current capacityinformation 1404 of the nDVR B may be exchanged via respective capacityexchange servers. The designated reconstitution location perchannel/resolution may be provided as information 1406. Information thatidentifies the closest nDVR per user/group may be provided as data 1407.The scores of rankings for where to reconstitute the segments may bedetermined and the results populated into the list 1405.

FIG. 15 shows an example of weighted, additive scoring method that maybe used in conjunction with step 1407 of FIG. 14. Other scoringprocesses may be used in addition to or in place of that described inFIG. 15. FIG. 15 shows a list of segments 1501 at resolutions R1/R2 attimes t0-t2 on the channel X for the users 1 and 2 of the Group G andthe user 3 of the Group H. The nDVR location indicated for archiving thechannel per resolution is indicated in the column 1502. The nDVR closestto the user/group may be indicated in the column 1503. The least loadednDVR may be indicated in the column 1504. Other information may beindicated in the column 1505. Other information may comprise aprobability of expected actual watching a recording or otherprobabilities. The weighting factors in FIG. 15 comprise 0.5, 1.6, 0.5,and 0.1, respectively. These weighting factors are provided forexplanatory purposes only and may be varied to adjust the scorings toalter the distributions of resulting locations as needed. The sums ofweighted values for the nDVR A may be indicated in the column 1506 andthe sum of weighted values for the nDVR B may be indicated in the column1507. The reconstitution location for each of the segments 1501 may bethe reconstitution location with the higher score of column 1506 andcolumn 1507. The reconstitution location may be represented in thecolumn 1508.

In FIG. 15, the nDVR A may be designated as the primary reconstitutionlocation of segments having resolution R1 while the nDVR B may bedesignated as the primary archiving location of segments havingresolution R2. The least loaded the nDVR may initially be the nDVR A,may shift to the nDVR B for time t1, and may return to the nDVR A fortime t2. The primary weighting factor in FIG. 13 may be the closest nDVRto the user/group of the column 1503. The reconstitution of the segmentsmay follow that closest to user/group location of the column 1503.

FIG. 16 shows a block diagram of an example nDVR, such as those as shownin FIGS. 3 and 4, with additional components. FIG. 16 shows an exampleof a system, such as a cloud or network DVR system, by which a serviceprovider, such as, but not limited to, a cable television serviceprovider, may receive a request to record content, store the requestedcontent, and potentially fulfill a request to deliver the requestedcontent for playback. The request to record a content item may bereceived from a device 1606 and the requested content item may bedelivered to the device 1606 for playback. As used herein, the device1606 may refer to a hardware element (such as a set-top cable box, astreaming-video player, a quadrature amplitude modulation (QAM) client,and/or other computing device) or a software element (such as a webbrowser or other software adapted to playback video). The device 1606used to request that the content item be recorded in the system may bedistinct from the device 1606 used to receive the recorded content itemfor playback. For example, a user may use his or her set-top cable boxto request that a particular content item be recorded, but may laterrequest and playback the content item with software running on his orher smart phone. The device 1606 may be connected to the system via anysuitable network, which may comprise a cable network, satellite network,and/or the Internet.

The system may comprise a guide scheduling server 1607. The guidescheduling server 1607 may receive and fulfill a request from the device1606 of a user to deliver a recorded content item to the device 1606 forplayback. The request from the device 1606 to deliver the content itemmay comprise identifications of the user (e.g., an account identifier, ausername and/or a password), the device 1606, the requested contentitem, and/or a playback time point or temporal location (e.g., the startof content or the 12:30 mark in a 30:00 minute content item). Therequest to deliver the content item may reflect a user skipping to aparticular portion of content of which the initial segments of thecontent item have already been delivered and are being played on thedevice 1606. A user may have started viewing the first minute of contentand may have decided to skip to a midway point of the content item. Inthis case, the request to deliver the content item may indicate that thedevice 1606 required the segments of the content item from that midwaypoint and the remaining portion of the content item. Based on receivinga request to deliver a content item to the device 1606, the guidescheduling server 1607 may provide one or more manifest files to thedevice 1606 that describe the content item and segments thereof,comprising network locations from which each segment may be downloaded.Using the manifest file, the device 1606 may iteratively download thesegments comprising the content item. The device 1606 may downloadsufficient segments of the content item, and the device 1606 may beginplayback of the content item.

The system may comprise a transcoder 1602. The transcoder 1602 mayreceive content from a content source 1601. The content item may be inany one of a variety of formats, such as H.264, MPEG-4 Part 2, or MPEG-2or other formats. The transcoder 1602 may convert the content item fromone video format to another video format, such as one amenable to themeans by which the service provider's users view the content. Thetranscoder 1602 may additionally segment the content item into aplurality of segments. Content may be segmented into a series of2-second segments or other segments of a period of time.

The transcoder 1602 may be in communication with a linear packager 1603and a linear storage 1604. The linear packager 1603 and the linearstorage 1604 may be in communication. The linear packager 1603 andlinear storage 1604 may refer generally to one or more interconnectedservers, storage devices, logical elements, and the like. The contentstored in linear storage 1605 may be served to requesting devices vialinear server 1605.

The linear packager 1603 may receive the content item from thetranscoder 1602. The linear packager 1603 may determine how the contentitem is to be segmented and put together for delivery to and eventualplayback by the device 1606. As part of this process, the linearpackager 1603 may segment the content item (such as in the event thatthe content item has not yet been segmented) or may re-segment thecontent item (such as in the event that the content item had beenpreviously segmented). The linear packager 1603 may additionally insertone or more cues or markers into the segments at which one or moreadditional segments, such as segments comprising an advertisement, maybe inserted by an upstream client, server, or logical module, such asthe device 1606 or the media recorder server 1609.

The linear packager 1603 may generate a manifest file associated withthe content item. Generally, a manifest file may contain informationdescribing various aspects of the associated content item that may beuseful for the device 1606 to playback the content item and/or for themedia recorder server 1609 to store and retrieve the content item. Amanifest file may indicate the segments comprising the content item, thelength of each segment, the quantity of segments, and/or the properordering of the segments necessary to allow a playback of the contentitem. A manifest file may further comprise a network location (e.g., ahypertext transfer protocol (HTTP) uniform resource locater (URL) linkor other universal resource identifier (URI)) for each segment fromwhich the segment may be downloaded, accessed, or retrieved. The networklocation may indicate a location on the linear storage 1604 or recordingstorage 1611. The network locations included within a manifest file maypoint to more than one different location or source. The networklocation for segments corresponding to the content item may reference alocation on the linear storage 1604 while the network location forsegments corresponding to an inserted advertisement may reference alocation from outside the system. A manifest file may describe multipleversions (e.g., different quality levels) of the content item and maycomprise corresponding information on those segments. A manifest filemay be provided, such as by the guide scheduling server 1607, to thedevice 1606 in response to a request to receive content recorded withinthe system. The device 1606 may use the manifest file to determine thesegments required to play the content item or a portion of the contentitem and subsequently download the required segments using the networklocations specified in the manifest file.

The content item or portions thereof may be stored in the linear storage1604, which may be accessed by the device 1606 directly or indirectlyvia the recording server 1609 to deliver the content item to the device1606. The linear storage 1604 may comprise one or more data storagedevices, such as volatile memory (e.g., random access memory (RAM)), ahard disk drive, a network-attached storage (NAS), and/or a storage areanetwork (SAN) in which the content item or portions thereof may bestored.

A media recorder server 1609 may be in communication with the channelmonitor server 1608. The media recorder server 1609 may serve tocoordinate the generation and retrieval of unique duplicate content itemrecordings. In particular, the media recorder server 1609 may coordinatethe simultaneous generation of multiple duplicate content itemrecordings of one or more content items. This coordination may be basedon a minimum quantity of users having requested recording of aparticular content item. The media recorder server 1609 may receive oneor more requests from devices 1606 to record content. The request torecord content may comprise identifications of the user (e.g., anaccount identifier, a username, and/or a password), the device 1606, thecontent item, the station/channel, the linear stream (from the linearstorage 1604 and/or from the linear server 1605), the start time of thecontent item, and/or the end time of the content item. Based onreceiving a request to record content, the media recorder server 1609may access a copy of the segments from one or more of the channelmonitor server 1608, the linear packager 1603, and/or the linear storage1604. The media recorder server 1609 may prepare to store a recording ofthe content item in a recording storage 1611. The recording storage 1611may comprise one or more storage devices, such as a hard disk drive, anetwork-attached storage (NAS), and/or a storage area network (SAN).

The media recorder server 1609 may comprise a plurality of mediarecorder servers (shown as stacked servers behind media recorder server1609), which may each represent a pool of resources available toindependently perform a recording task, such as writing copies of asegment to the recording storage 1611. A higher level media recorderserver (a first of media recorder servers 1609) may oversee theoperations of lower media recorder servers (second and subsequent mediarecorder servers 1609) to track and maintain the status of each of thelower media recorder servers. The higher media recorder server may, atany given time, know which lower media recorder servers are busyperforming a recording task and which are available to be assigned arecording task to perform. As each of the lower media recorder serverscompletes a recording task, the lower media recorder server may indicateto the higher media recorder server 1609 that the lower media recorderserver is now available. Alternatively, each of the media recorderservers 1609 may maintain each of the other media recorder servers' 1609respective state (e.g., busy, available, etc.) instead of the higher ofthe media recorder server 1609 maintaining the state of each of thelower media recorder servers 1609. The media recorder servers 1609 mayindividually report their status to one or more channel monitor servers1608. A queue of available media recorder servers 1609 may bemaintained, such as by the channel monitor servers 1608 or by anotherserver. As one of the media recorder servers 1609, such as a third mediarecorder server 1609, becomes available, the media recorder server 1609may insert itself into the queue. As the channel monitor server 1608 orguide scheduling server 1607 or other server has a task to be performed,these servers may query the queue for the next available media recorderserver 1609 and assign the task to that media recorder server 1609.

The media recorder servers 1609 may access, such as from the linearstorage 1604, a segment of content that has been requested to berecorded. Based on this single access of the segment, the channelmonitor server 1608 may direct one of the available media recorderservers 1609 to write a copy of this segment to the recording storage1611 for each request for the content item to be recorded. As anexample, the third media recorder server 1609 may provide aninstruction, such as via a network socket, to the recording storage1611, wherein the instruction specifies the file of the segment and thenumber of times that the file is to be copied to the recording storage1611. The instruction may comprise an HTTP command, such as PUT, POST,or PATCH. In this manner, the segment may be written multiple times tostorage, but may be accessed only a single time. Thus, this may resultin a performance increase of the media recorder server 1609 and thesystem as a whole because the read operation of the segment from thelinear storage 1604 may occur a single time for all the segment copiesinstead of once for each segment copy. The third media recorder server1609 may indicate to the channel monitor server 1608 that the thirdmedia recorder server 1609 has successfully written the copies of thesegment and that the third media recorder server 1609 is available toperform another recording task. In the event that the third mediarecorder server 1609 is unsuccessful in its task (e.g., the recordingstorage 1611 indicates a disk error), the third media recorder server1609 may indicate this status to the channel monitor server 1608 and thechannel monitor server 1608 may direct the third media recorder server1609 to attempt to repeat the recording task or assign the recordingtask to another of the media recorder servers 1609, such as second mediarecorder server 1609. This method may be repeated until all segments ofthe content item are copied to the recording storage 1611 and there is acomplete copy of the content item in the recording storage 1611 for eachuser request to record the content item.

The channel monitor server 1608 may direct one of the media recorderservers 1609, such as the third media recorder server 1609, to writemultiple copies of a segment to disk. Since the channel monitor server1608 and the third media recorder server 1609 may know that the thirdmedia recorder server 1609 may write the same segment multiple times tothe recording storage 1611, this fact may be leveraged to moreefficiently perform the write operation. The channel monitor server 1608may direct the third media recorder server 1609 to write the multiplecopies of the segment in physical sequence on a hard disk of therecording storage 1611. By writing the multiple copies of the segment insequence, a head of the hard disk may seek a write location on a harddisk platter only once. In contrast, a non-sequential write operation toa hard disk may involve multiple seek operations and, thus, may takelonger to perform the write operation. In order to facilitate asequential write operation of multiple copies of a segment, the channelmonitor server 1608, the media recorder server 1609, and/or therecording storage 1611 may determine a total amount of storage required.This may comprise multiplying the quantity of copies of the segment thatare to be written (e.g., the quantity of pending user requests to recordthe content item containing the segment) by the size of the segment.With the total amount of storage determined, the channel monitor server1608, the media recorder server 1609, and/or the recording storage 1611may access information on the status of the hard disks of the recordingstorage 1611, such as which hard disk blocks or partitions are availablefor writing. With this information and the total amount of storagerequired, a location on the disk may be determined to perform thesequential write of the multiple copies of the segment.

A batching strategy may be determined, such as by the media recorderserver 1609, in which the multiple copies of a segment that are to bewritten to storage, such as the recording storage 1611, may be splitinto a plurality of sets or batches. The storage may be generallyrepresented as media storage 1610 that may comprise recording storage1611 and archive storage 1612. The splitting of the multiple copies ofthe segment into a plurality of batches may be based on a capacity oravailable capacity of a hard disk (or platter thereof) of the recordingstorage 1611 or a period of time in which the write operation mustcomplete. If 100,000 copies of a 10 megabyte (MB) segment are to bewritten to the recording storage 1611 and each of the hard disks of therecording storage 1611 have a capacity of 800 gigabytes (GB), the100,000 copies to be written may be split into ten batches of 10,000copies each. Each of the ten batches may be executed, such as by themedia recorder server 1609, to write the respective 10,000 copies of thesegment to a separate respective hard disk in sequence. Each of the tenbatches may be assigned by the channel monitor server 1608 to one of themedia recorder servers 1609 to be executed.

An archive storage 1612 may be in communication with the media recorderserver 1609 and/or the recording storage 1611, and may comprise one ormore storage devices, such as a hard disk drive, a network-attachedstorage (NAS), and/or a storage area network (SAN). The archive storage1612 may archive copies of content that have spent a certain amount oftime in the recording storage 1611. That is, if a certain amount of timepasses since content has been recorded and copies made in the recordingstorage 1611, the copies in the recording storage 1611 may be deletedand a single copy may be made in the archive storage 1612. If thearchived content item is requested by a user to be delivered to thedevice 1606 of the user for playback, the media recorder server 1609 mayaccess the copy of the content item in the archive storage 1612 and makea new copy of the content item in the recording storage 1611. The copyof the content item in the recording storage 1611 may be delivered tothe device 1606 of the user, either directly or via the recording server1609, which may be in communication with the recording storage 1611directly or via the media recorder server 1609.

The segmented nature of the content item may be leveraged to begindelivering the content item from the recording storage 1611 to thedevice 1606 before the content item is completely copied from thearchive storage 1612. Based on a user's request for delivery of contentarchived in the archive storage 1612, the media recorder server 1609 maybegin by copying the first segment of the content item to the recordingstorage 1611. The recording server 1609 need not wait until all segmentsof the content item are copied to the recording storage 1611 beforebeginning to deliver the content item to the device 1606, but mayinstead begin delivering the segments of the content item based on oneor more segments have been copied to the recording storage 1611. Themedia recorder server 1609 may continue copying subsequent segments(e.g., the second segment, the third segment, and so forth) of thecontent item to the recording storage 1611, which may be delivered tothe device 1606. Preferably, the subsequent segments may be copied fromthe recording storage 1611 to the archive storage 1612 and delivered tothe device 1606 at a rate sufficient for the playback of the segments onthe device 1606 to be seamlessly maintained. If the playback on thedevice 1606 is stopped or paused and no additional segments of thecontent item are requested, a full duplicate copy may still begenerated. The media recorder server 1609 may determine the segments ofthe content item that do not need to be delivered to the device 1606(e.g., segments preceding a mid-content item playback start point,segments that are skipped during playback, such as those for acommercial, and segments subsequent to a playback stop point) and havenot yet been copied to the recording storage 1611. Those segments may becopied from the archive storage 1612 to the recording storage 1611 toreconstitute the entire unique copy of the content item.

Capacity exchange server 1615 may gather current usage information frommedia storage 1610 (e.g., disk reads status, max disk reads capacity,disk writes status, and max disk writes capacity), current usageinformation from channel monitor servers 1608 and media recorder servers1609 (e.g., compute network status and max compute network capacity),and media recorder servers 1609 (e.g., disk network status and max disknetwork capacity). This capacity information may be collected asdescribed with respect to FIG. 5B and the capacity exchange server 1615may exchange this capacity information with other network digital videorecording systems.

FIG. 17 shows an example of a method 1700 for recording unique copies ofsegments based on user requests to record the content item. At step1701, a number (N) of requests to record content may be received by theguide scheduling server 1607. The request may be provided by one or moredevices 1606 associated with one or more users. A request to record thecontent item may be a real-time request, such as while a user iswatching content and impulsively decides to record the content item. Arequest to record the content item may be a scheduled request. Ascheduled request may be based on a user navigating a displayedtelevision schedule and selecting a content item showing at a futuretime to be recorded. In the event that scheduled requests are managed bya scheduling module within the guide scheduling server 1607, thescheduling module may provide the request to record to the channelmonitor server 1608 at the time that the content item is shown. Therequest to record content may comprise identifications of the user(e.g., an account identifier, a username, and/or a password), the device1606, the content item, the station/channel, the linear stream (from thelinear storage 1604 and/or from the linear server 1605), the start timeof the content item, and/or the end time of the content item.

At step 1702, segment information associated with the content item maybe accessed or received by the channel monitor server 1608. Concurrentto the requests for recording the content item being received, thecontent item may be received by the system from the content source 1601,wherein the content item is transcoded and segmented into segments. Oneor more manifest files may additionally be generated that describe thesegmentation of the content item and a location of each segment makingup the content item, such as a location in the linear storage 1604.Showing possible accessing or receiving segment information, the channelmonitor server 1608 may access or receive, such as from the linearstorage 1604, the manifest file associated with the content item.

At step 1703, based at least on the segment information, a segment ofthe content item may be determined, such as by the channel monitorserver 1608, that will be copied to storage, such as the recordingstorage 1611. The channel monitor server 1608 may use the manifest fileassociated with the content item to extract the necessary segmentinformation. The manifest file may indicate the total quantity ofsegments making up the content item or a portion of the content item,the length of the content item, the length of each segment, and an orderor sequence of the segments. Based on the segment information and also,which, if any, segments of the content item have already been copied tostorage, the channel monitor server 1608 may determine a segment of thecontent item to copy to storage. If the request to record content wasfor a complete content item (e.g., a scheduled request) and no segmentsof the content item had yet been determined and copied to storage, thechannel monitor server 1608 may determine the first segment as thesegment to copy to storage. Alternatively, if the first X segments ofthe content item had already been copied to storage, the channel monitorserver 1608 may determine the next segment (e.g., the segment at the X+1position in the sequence of segments) as the segment to copy to storage.

A reference to a copy, such as a copy of a segment, may refer to asecond segment that comprises at least a portion of the originalsegment. A reference to a copy is not so limited as to require that acopy of a segment be identical in all regards to the original segment.Similarly, a reference to copying, such as copying an original segment,may refer to the act of generating a second segment that comprises atleast a portion of the original segment. Moreover, a copy may be inreference to the content of content or segment without regard to form. Astored version of content in standard definition may be considered to bea copy of a stored version of the same content item in high definition.Two segments of the same content may be considered to be copies of eachother although the first segment may be in one video format, such asH.264, and the second segment may be in another video format, such asH.262.

At step 1704, one of the media recorder servers 1609, such as the thirdmedia recorder server 1609, may be assigned by the channel monitorserver 1608 to copy the determined segment of the content item tostorage, such as the recording storage 1611, N times (e.g., one time foreach user request to record the content item). The channel monitorserver 1608 may maintain the status (e.g., busy, available, etc.) ofeach of the media recorder servers 1609. Based on the channel monitorserver 1608 assigning one of the media recorder servers 1609, such asthe third media recorder server 1609, to write a segment to storage orperform some other task, the channel monitor server 1608 may designatethe third media recorder server 1609 as busy. After the third mediarecorder server 1609 completes the task, the third media recorder server1609 may be designated as available. As the channel monitor servers 1608(or other server) may track the status of each of the media recorderservers 1609, the channel monitor server 1608 may thus ascertain whichof the media recorder servers 1609 is available.

The channel monitor server 1608 need not maintain the state of each ofthe media recorder servers 1609. Each of the media recorder servers 1609may maintain each of the other media recorder servers' 1609 respectivestate. If one of the media recorder servers 1609, such as third mediarecorder server 1609, completes a task and transitions to an availablestate, the third media recorder server 1609 may insert itself into aqueue of available media recorder servers at each channel monitor server1608. If the channel monitor server 1608 has a task to be performed,such as writing copies of a segment to the recording storage 1611, thechannel monitor server 1608 may query the queue of available mediarecorder servers and assign the task to the media recorder server at thetop of the queue.

A separate queue in another server may maintain each media recorderservers' 1609 respective state. If one of the media recorder servers1609, such as the third media recorder server 1609, is available basedon completing a task, the third media recorder server 1609 may soindicate to the other server(s) and/or request an additional task fromthe other server(s). The other server(s) may maintain a pool of pendingtasks and assign a task from the pool to the third media recorder server1609 in response to a request from the third media recorder server 1609.

Based on a determination of an available media recorder server, whichmay be accomplished by a query of a queue of available media recorderservers, a request from an available media recorder server, or othermethod, the media recorder server 1609 may assign the determined mediarecorder server to copy the determined segment to the recording storage1611 N times. As part of the assignment, the media recorder server 1609may issue a command to the media recorder server to make N copies of thesegment. The media recorder server 1609 may issue an HTTP POST commandto the media recorder server that comprises a content identifier (e.g.,a stream ID), a segment identifier (e.g., a start time, a stop time,and/or a duration of the segment), a segment file location (e.g., a URLor URI pointing to a file location on the linear storage 1604 or otherstorage), and a number of times to copy the segment to the recordingstorage 1611.

At step 1705, the assigned media recorder server, such as the thirdmedia recorder server 1609, may access or receive the segment from thelinear storage 1604 a single time. The access or receipt may be based oninformation included in the command from the media recorder server 1609,such as the content item identifier, the segment identifier, and/or thesegment file location (e.g., the segment URI).

At step 1706, the assigned media recorder server, such as the thirdmedia recorder server 1609, may generate N copies of the segment instorage, such as the recording storage 1611. This operation may be basedoff the single access or receipt of the segment from the linear storage1604. The number of copies (e.g., N copies) may be specified in thecommand issued to the media recorder server from the media recorderserver 1609. As part of generating N copies of the segment in therecording storage 1611, the third media recorder server 1609 may issuean HTTP PUT command to the recording storage 1611 that comprises a filelocation of the segment and the number of copies (e.g., N copies) of thesegment to be made in the recording storage 1611. The N copies of thesegment may be generated in the recording storage 1611 such that the Ncopies of the segment are written to a hard disk of the recordingstorage 1611 in physical sequence.

The assigned media recorder server, such as the third media recorderserver 1609, may notify the channel monitor 1608 that the assigned mediarecorder server has successfully completed generating N copies of thesegment in storage and that the assigned media recorder server isavailable. The channel monitor server 1609 may repeat step 1703 anddetermine another segment of either the same content item or anothercontent item and repeat steps 1704 through 1706 for that segment.Multiple performances of steps 1703 through 1704 may occursimultaneously with different media recorder servers 1609 across thegroup of channel monitor servers 1608. The channel monitor servers 1608for different channels may determine multiple different segments ofcontent and assign each of the different segments to a different mediarecorder server (e.g., a first media recorder server 1609, a secondmedia recorder server 1609, and the third media recorder server 1609) tobe copied to storage. Each of the media recorder servers 1609 maysimultaneously and/or independently access or receive their respectivesegment and generate N copies of the respective segment in storage. Themethod 1700 is not limited to performance in connection with a singlecontent item and may be performed with respect to multiple content itemssimultaneously being requested to be recorded and copies of each beingmade in storage.

The following is a possible operation of the method 1700. A populartelevision show may be scheduled to be shown on an upcoming Sundaynight. One hundred users of a system may log into the system andschedule for the television show to be recorded within the system on theSunday night. On Sunday night, media recorder server 1609 may record adiscrete copy of the content item for each of the one hundred requestingusers. As the television show is received by a content source, thetelevision show, or a portion thereof, may be broken into a number ofsegments, such as 30 2-second segments representing a 60-second rollingportion of the television show, and the segmentation may be documentedin a separate file, such as a manifest file. Channel monitor server 1608within the system may access the manifest file to determine a segment tocopy to a recording storage, such as the recording storage 1611. If nosegments have yet to be copied to the recording storage 1611, thechannel monitor 1608 may select the first segment of the televisionshow. In order to copy the first segment of the television show, thechannel monitor server 1608 may perform a query of its media recorderservers to determine which media recorder servers are available andassign the copying task to an available media recorder server. Theassigned media recorder server may generate one hundred copies of thefirst segment (once for each requesting user) in the recording storage1611 by performing a single access of the first segment and commandingthe recording storage 1611 to write the first segment, in sequence onthe recording storage's 1611 hard disk, one hundred times. The assignedmedia recorder server may notify the channel monitor server 1608 that itis available after completion of the task. The channel monitor server1608 may continue to assign available media recorder servers to generateone hundred copies of subsequent segments (e.g., the second segment, thethird segment, etc.) in the recording storage 1611 for each of the 30segments of the portion of the television show. The method may berepeated for subsequent 60-second portions of the television show untilthe complete television show is recorded. If one of the one hundredusers wishes to view the user's stored version of the television show,the copy of the segments (associated with the user) of the televisionshow may be delivered from the recording storage 1611 to the user'sdevice, such as the device 1606, for playback.

FIG. 18A is a possible representation of three recordings 1800, 1820,1840 of content that are to be made based on three requests to recordthe content item received by the system. Each of the three recordings1800, 1820, 1840 may comprise one or more sequential segments,designated as A, B, C, and/or D (e.g., 1800A, 1800B, and so forth).1800B and 1840B may be identical segments, 1800C, 1820C, and 1840C maybe identical segments, and so forth. The first recording 1800 may havebeen based on a scheduled request and may comprise all segments of thecontent item. The second recording 1820 and the third recording 1840 mayeach have been based on a real-time or impulse recording and each maylack one or more of the initial segments (e.g., the A segment).

FIG. 18B shows a representation of the three recordings 1800, 1820, 1840in storage. Each of the three recordings 1800, 1820, 1840 may have beenretrieved from content that was received and stored in the linearstorage 1604 and written to the recording storage 1611 independently.The B segment in the linear storage 1604 for segment 1800B may beaccessed, the recording storage 1611 may seek an open location on one ofits hard disks, and a copy may be written to the open location on thehard disk of the recording storage 1611. Independently, the B segment inthe linear storage 1604 for segment 1840B may also be accessed, therecording storage 1611 may seek another location on one of its harddisks, and a copy may be also written to the location on the hard diskof the recording storage 1611. In this manner, the generation of segment1800B and segment 1840B may require two accesses of linear storage, twohard disk seek operations, and two hard disk write operations.Extrapolating this method to the other segments of the three recordings1800, 1820, 1840 may result in a total of nine accesses of linearstorage 1604, nine hard disk seek operations, and nine hard disk writeoperations.

FIG. 18C shows another representation of the recordings 1800, 1820, 1840in storage. In this representation, common segments (e.g., 1800B and1840B or 1800C, 1820C, and 1840C, etc.) may be grouped together foraccessing and writing to storage. The media recorder server 1609 mayassign a media recorder server, such as first media recorder server1609, to write segment 1800A to the recording storage 1611. The firstmedia recorder server 1609 may access the A segment in the linearstorage for segment 1800A and may direct the recording storage 1611 togenerate one copy of the A segment. The recording storage 1611 may seekan open location on one of its hard disks for the one copy of the Asegment, and a copy of the A segment may be written to the open locationon the hard disk of the recording storage 1611. This operation mayrequire one linear storage access, one hard disk seek operation, and onehard disk write operation. The media recorder server 1609 may assign asecond media recorder server 1609, to write segments 1800B and 1840B tothe recording storage 1611. The second media recorder server 1609 mayaccess the B segment in the linear storage 1604 a single time and maydirect the recording storage 1611 to generate two sequential copies ofthe B segment. The recording storage 1611 may seek an open location onone of its hard disks sufficient to accommodate the two copies of the Bsegment and may perform a single write operation comprising the twocopies of the B segment (one each for segments 1800B and 1840B). Despitegenerating two copies of the B segment, this operation may be achievedwith one linear storage 1604 access, one hard disk seek operation, andone hard disk write operation. The media recorder server 1609 may assigna third media recorder server, such as third media recorder server 1609,to write segments 1800C, 1820C, and 1840C to the recording storage 1611.The media recorder server 1609 may access the C segment in the linearstorage 1604 a single time and may instruct the recording storage 1611to generate three sequential copies of the C segment. The recordingstorage 1611 may seek an open location on one of its hard diskssufficient to fit the three copies of the C segment. The recordingstorage 1611 may perform a single write operation comprising the threecopies of the C segment (one each for segments 1800C, 1820C, and 1840C).Despite generating three copies of the C segment, this operation may beachieved with one linear storage 1604 access, one hard disk seekoperation, and one hard disk write operation. The method may besimilarly performed for segments 1800D, 1820D, and 1840D. In total,generating the three recordings 1800, 1820, and 1840 may be achieved byfour linear storage 1604 accesses, four hard disk seek operations, andfour hard disk write operations.

The representation of FIG. 18C is in contrast to the representation ofFIG. 18B. The method used to generate the arrangement of FIG. 18B andthe method used to generate the arrangement of FIG. 10C may both resultin the three recordings 1800, 1820, 1840 being generated in therecording storage 1611. The method used to generate the arrangement ofFIG. 18B may perform the task with nine each of linear storage 1604accesses, hard disk seek operations, and hard disk write operations; themethod used to generate the arrangement of FIG. 18C may perform the taskwith four each of linear storage 1604 accesses, hard disk seekoperations, and hard disk write operations. The method used to generatethe arrangement of FIG. 18C, such as the method 1700 of FIG. 17, mayresult in a significant performance increase for a computer or series ofcomputers on which the media recorder server 1609 operates and/or forthe recording storage 1611.

FIG. 19 shows an example of a method for delivering a content item, orportion thereof, to the device 1606 after a requesting user's uniquecopy is moved from a storage from which the content item may bedelivered, such as the recording storage 1611, to an archive storage,such as the archive storage 1612. The copy of the content item in thearchive storage 1612 may be a consolidated (i.e., not unique) copy ofone or more unique recordings that were present in the recording storage1611 but have since been removed after a certain period of time haspassed since the recording(s) was made and/or last accessed in therecording storage 1611. If a user requests to playback the archivedcontent item, a unique copy of the content item may be generated, suchas in the recording storage 1611, for the requesting user. If the userdoes not playback the entire content item, such as if the user beginsplayback of the content item in the middle of the content item, andskips ahead in the content item (e.g., to skip a commercial), or theuser ends the playback prematurely, the unique copy of the entirety ofthe content item may still be generated. In the method 1900, thesegmented nature of content within the system may be leveraged tofacilitate delivery and playback of the content item while the uniquecopy of the content item is generated.

At step 1901, a request to deliver an archived content item at aspecified time point (e.g., a temporal location) in the content item maybe received by the recording server 1609. The request may be made by auser and be received from the device 1606 of the user. The specifiedtime point may indicate the start time of the content item or it mayindicate a time point within the middle of the content item (e.g., the10:30 mark in a 30:00 minute content item). The request to deliver anarchived content item may reflect the user initiating the playback ofthe content item (whether from the beginning or the middle of thecontent item) or may reflect the user skipping ahead or backwards withinthe content item. The request may further comprise identifications ofthe user (e.g., an account identifier, a username, and/or a password),the device 1606, and/or the content item. Based on receiving therequest, the recording server 1609 may communicate the request to themedia recorder server 1609.

At step 1902 and based, at least, on the time point specified in therequest, a segment of the content item may be determined by the mediarecorder server 1609. The determined segment may be intended to beassociated with the requesting user. The association with the requestinguser may be exclusive with respect to other users. To determine anappropriate segment, the media recorder server 1609 may reference amanifest file associated with the content item. For example, thespecified time point may be cross-referenced with a listing in themanifest file of the segments of the content item and each of theirassociated time intervals to determine which of the segments correspondsto the specified time point. If one or more segments have already beendetermined, copied from the archive storage 1612, and delivered, thesegment may be determined with consideration to those previousiterations. For example, if the initial segment corresponding to thespecified time point and the subsequent two segments have already beencopied from the archive storage 1612 and delivered, the third segmentafter the initial segment may be determined.

At step 1903, the determined segment may be copied from an archivestorage, such as the archive storage 1612, to a storage appropriate fordelivery of the segment and/or for maintaining the complete unique copyof the content item, such as the recording storage 1611. The copy of thesegment in the recording storage 1611 may be associated with therequesting user. The association may be exclusive with respect to otherusers. The copying from the archive storage 1612 to the recordingstorage 1611 may be performed by or otherwise facilitated by the mediarecorder server 1609. The newly-copied segment may be combined orotherwise associated (such as a logical linking of linearly contiguoussegments making up the content item or a portion thereof) with othersegments of the content item in the recording storage 1611. For example,if prior segments of the content item have already been copied to therecording storage 1611, the newly-copied segment may be combined orotherwise associated with those prior segments.

At step 1904, the segment may be delivered from the recording storage1611 to the device 1606 for playback. The delivery may be direct (e.g.,the device 1606 downloads directly from the recording storage 1611) orindirect. As an example of an indirect delivery, the media recorderserver 1609 may provide the segment to the recording server 1609, fromwhich the segment may be delivered to the device 1606.

After the segment of the content item is delivered to the device 1606from the recording storage 1611, steps 1902 through 1904 may be repeatedfor subsequent segments of the content item necessary to effectuate therequested playback of the content item. For example, if a user requestedthat content commence playback at the 10:00 (i.e., the ten minute, zerosecond) time point and the segments of the content item are two secondseach in length, the initial steps 1902 through 1904 may comprisedetermining a first segment for 10:00 to 10:02, copying the firstsegment from the archive storage 1612 to the recording storage 1611, anddelivering the first segment to the device 1606. A second iteration ofsteps 1902 through 1904 may comprise determining a second segment for10:02 to 10:04, copying the second segment from the archive storage 1612to the recording storage 1611, and delivering the second segment to thedevice 1606. The iterative method may be repeated until the user stopsplayback of the content item or the final segment of the content item isdelivered.

At step 1905, a segment may be determined, by the media recorder server1609, that has not yet been copied from the archive storage, such as thearchive storage 1612, to the storage that will maintain the unique copyof the content item for the requesting user, such as the recordingstorage 1611. The determined segment may be intended to be associated,exclusively with the requesting user. The determination may occur basedon the completion of one or more iterations of steps 1902 through 1904.For example, if the user requested playback (and therefore delivery) ofcontent at a mid-point of the content item, the segments from themid-point of the content item to the end of the content item may havebeen copied from the archive storage 1612 to the recording storage 1611in one or more iterations of steps 1902 through 1904. Therefore, themedia recorder server 1609 may determine a segment from before thespecified mid-point of the content item.

At step 1906, the determined segment of step 1905 may be copied from thearchive storage 1612 to the recording storage 1611. The copy of thesegment in the recording storage 1611 may be associated with therequesting user. The association may be exclusive with respect to otherusers of the system. The copying from the archive storage 1612 to therecording storage 1611 may be performed by or otherwise facilitated bythe media recorder server 1609. The segment may be combined or otherwiseassociated (such as a logical linking of linearly contiguous segmentsmaking up the content item or a portion thereof) with other segments ofthe content item in the recording storage 1611. For example, the segmentcopied in step 1906 may be combined or otherwise associated with one ormore segments copied in step 1903 or with one or more segments copied inprior iterations of step 1906.

Steps 1905 through 1906 may be repeated for other segments that had notyet been copied from the archive storage 1612 to the recording storage1611, such as those copied in one or more iterations of steps 1902through 1904 and/or prior iterations of steps 1905 through 1906.Continuing the example of the user requesting playback from themid-point of the content item and the segments from the mid-point to theend of the content item already being copied to the recording storage1611, steps 1905 through 1906 may be repeated multiple times until eachof the segments prior to the mid-point are copied from the archivestorage 1612 to the recording storage 1611. In this manner, all segmentscomprising the content item, and thus the entirety of the content itemitself, may be copied to the recording storage 1611.

The following is a non-limiting example of the operation of the method1900. A system user may have recorded a television show several monthsprior and may not have viewed it in the interim. The user's copy of thetelevision show that was initially made in a recording storage, such asthe recording storage 1611, may have been removed from the recordingstorage 1611 and there may exist only a copy in an archive storage, suchas the archive storage 1612, that is not uniquely associated with theuser. If the user requests playback of the television show, the entiretyof the unique copy of the television show may be regenerated in therecording storage 1611, even if the user does not request the entiretyof the television show for playback. The user may, for example, requestthat the system deliver the recorded television show for playback at amidway point in the show (the user may have watched the beginning of thetelevision show when it was originally shown). A recording managementsystem, such as the media recorder server 1609, of the system maydetermine the segment of the television show corresponding to the midwaytime point and copy that segment from the archive storage 1612 to therecording storage 1611. The copy of the segment in the recording storage1611 may be delivered to the user's device, such as the device 1606, forplayback. The media recorder server 1609 may determine, copy to therecording storage 1611, and deliver subsequent segments of thetelevision show until the end of the television show is reached.Independent of the determining, copying, and delivery of the segmentscomprising the television show from the midway point and on, thesegments of the television show prior to the midway point (which do notneed to be delivered to the user's device) may also be copied to therecording storage 1611. The media recorder server 1609 may determine thefirst segment of the television show and generate a copy of that segmentfrom the archive storage 1612 and send it to the recording storage 1611.The media recorder server 1609 may repeat this for subsequent segmentsuntil the midway point of the television show is reached. In thismanner, the whole copy of the television show may be regenerated in therecording storage 1611, even though the user was able to begin playbackof the television show at the midway point before the whole copy wasmade.

FIG. 20 shows example representations of operations that may beperformed in content recordings, such as described in FIG. 19, forfulfilling a request to deliver an archived content item starting at aspecified time point and copying the content item from the archivestorage 1612 to the recording storage 1611. Representations of content2000 and its segments 2001-2014 are shown at succeeding times t1-t5. InFIG. 20, segments that are not yet copied from the archive storage 1612to the recording storage 1611 are unshaded and segments that have beencopied from the archive storage 1612 to the recording storage 1611 arepatterned.

At time t1, a user may decide to begin playback of the archived contentitem 2000 from the beginning and, therefore, a request may be receivedto deliver the content item 2000 with a specified time point for thebeginning of the content item 2000. Segment 2001 may be determined tocorrespond to the beginning of the content item 2000. Segment 2001 maybe copied from the archive storage 1612 to the recording storage 1611and segment 2001 may be delivered to the user's device 1606 forplayback. The copying of segment 2001 to storage is representing by thepatterned state of segment 2001.

At time t2, the user may have continued watching the content item 2000and segment 2002 may have been delivered to the user's device 1606 andcopied to the recording storage 1611, as reflected in the patternedstate of segment 2002. After viewing segment 2002, the user may decideto skip ahead to a mid-point in the content item 2000 corresponding tosegment 2007. Segment 2007 may be copied to the recording storage 1611,as reflected in the patterned state of segment 2007, and subsequentlydelivered to the user's device 1606 for playback.

At time t3, the user may have continued watching the content item 2000from the mid-point of the content item 2000. Thus, segment 2008 may havebeen copied to the recording storage 1611, reflected in the patternedstate of segment 2008, and delivered to the user's device 1606 forplayback. After viewing segment 2008, the user may skip ahead, such asto skip a commercial, to a later point in time of the content item 2000corresponding to segment 2010. Segment 2010 may be copied to therecording storage 1611, as reflected in the patterned state of segment2010, and may be delivered to the user's device 1606 for playback.

At time t4, the user may have watched the content item until itsconclusion and, thus, the remaining segments, segments 2011-2014 mayhave been copied to the recording storage 1611, reflected in thepatterned state of segments 2011-2014, and delivered to the user'sdevice 1606 for playback. At this time, the user's request to receiveand playback the content item 2000 may have been fulfilled, but acomplete unique copy of the content item 2000 may not yet be generatedbecause segments 2003-2006 and 2009 may have not yet been copied to therecording storage 1611.

At time t5, segments 2003-2006 and 2009 may be determined as not havingyet been copied to the recording storage 1611 and, therefore, may becopied from the archive storage 1612 to the recording storage 1611, asreflected in the patterned state of segments 2003-2006 and 2009. As canbe seen at time t5, all segments may now have been copied to therecording storage 1611, thus forming a complete unique copy of thecontent item 2000.

The servers may comprise separate storage units and high capacityprocessing units or combined units or both. The storage units maycomprise moving disks and/or solid state storage technologies. Theprocessing units in the servers may implement the channel monitoring,media recording, metadata indexing, and capacity exchange functions.Ratios of the processing servers to the storage servers may be 1:10 forstandard resolution recordings with the ratio changing to higher storagefor higher resolution recordings including but not limited to 1:20,1:30, and other ratios.

As used in the specification and the appended claims, the singular forms“a,” “an,” and “the” include plural referents unless the context clearlydictates otherwise. Ranges may be expressed herein as from “about” oneparticular value, and/or to “about” another particular value. When sucha range is expressed, another possibility includes from the oneparticular value and/or to the other particular value. Similarly, whenvalues are expressed as approximations, by use of the antecedent“about,” it will be understood that the particular value forms anotheroption. It will be further understood that the endpoints of each of theranges are significant both in relation to the other endpoint, andindependently of the other endpoint.

Throughout the description and claims of this specification, the word“comprise” and variations of the word, such as “comprising” and“comprises,” means “including but not limited to,” and is not intendedto exclude other components, integers or steps. “Such as” is not used ina restrictive sense, but for explanatory purposes.

Components are described that may be used to perform the describedmethods and systems. When combinations, subsets, interactions, groups,etc., of these components are described, it is understood that whilespecific references to each of the various individual and collectivecombinations and permutations of these may not be explicitly described,each is specifically contemplated and described herein, for all methodsand systems. This applies to all aspects of this application including,but not limited to, operations in described methods. Thus, if there area variety of additional operations that can be performed it isunderstood that each of these additional operations can be performedwith any specific embodiment or combination of embodiments of thedescribed methods.

As will be appreciated by one skilled in the art, the methods andsystems may take the form hardware, of software, or a combinationsoftware and hardware. The methods and systems may take the form of acomputer program product on a computer-readable storage medium havingcomputer-readable program instructions (e.g., computer software)embodied in the storage medium. The methods and systems may take theform of web-implemented computer software. Any suitablecomputer-readable storage medium may be utilized including hard disks,CD-ROMs, optical storage devices, or magnetic storage devices.

Methods and systems are described with reference to block diagrams andflowcharts of methods, systems, apparatuses, and/or computer programproducts. It will be understood that each block of the block diagramsand flowcharts, and combinations of blocks in the block diagrams andflowcharts, respectively, can be implemented by computer programinstructions. These computer program instructions may be loaded on ageneral-purpose computer, special-purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions that execute on the computer or other programmable dataprocessing apparatus create a means for implementing the functionsspecified in the flowchart block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented method suchthat the instructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain methods or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically described, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed.Systems and components described herein may be configured differentlythan described. For example, elements may be added to, removed from, orrearranged.

Various items may be described as being stored in memory or on storagewhile being used. These items or portions thereof may be transferredbetween memory and other storage devices for purposes of memorymanagement and data integrity. Some or all software modules and/orsystems may execute in memory on another device and communicate with thevarious computing systems via inter-computer communication. Some or allof the systems and/or modules may be implemented or provided in otherways, such as at least partially in firmware and/or hardware, including,but not limited to, one or more application-specific integrated circuits(“ASICs”), standard integrated circuits, controllers (e.g., by executingappropriate instructions, and including microcontrollers and/or embeddedcontrollers), field-programmable gate arrays (“FPGAs”), complexprogrammable logic devices (“CPLDs”), etc. Some or all modules, systems,and data structures may also be stored (e.g., as software instructionsor structured data) on a computer-readable medium, such as a hard disk,a memory, a network, or a portable media article to be read by anappropriate device or via an appropriate connection. Systems, modules,and data structures may be transmitted as generated data signals (e.g.,as part of a carrier wave or other analog or digital propagated signal)on a variety of computer-readable transmission media, comprisingwireless-based and wired/cable-based media, and may take a variety offorms (e.g., as part of a single or multiplexed analog signal, or asmultiple discrete digital packets or frames). Computer program productsmay also take other forms.

Unless otherwise expressly stated, methods do not require operations tobe performed in a specific order. Accordingly, where a method claim doesnot actually recite an order to be followed by its operations or it isnot otherwise specifically stated in the claims or descriptions that theoperations are to be limited to a specific order, it is no way intendedthat an order be inferred, in any respect. This holds for any possiblenon-express basis for interpretation, including: matters of logic withrespect to arrangement of steps or operational flow; plain meaningderived from grammatical organization or punctuation; and the number ortype of alternatives or modifications described in the specification.

Implementations of the disclosure may be instantiated in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules may comprise routines, programs,objects, components, data structures, etc. that perform particular tasksor implement particular abstract data types when executed by a processorin a computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid-statememory, RAM, etc. The functionality of the program modules may becombined or distributed. In addition, the functionality may be embodiedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more concepts of the disclosure, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the disclosure. Accordingly, theforegoing description is by way of example only, and is not limiting.

The invention claimed is:
 1. A method comprising: determining, by afirst network digital video recorder (nDVR), first capacity informationindicating a utilization associated with the first nDVR; receiving, bythe first nDVR, second capacity information indicating a utilizationassociated with a second nDVR; and storing, by the first nDVR and basedon the first capacity information and the second capacity information,one or more content segments.
 2. The method of claim 1, furthercomprising: determining, by the first nDVR and based on the firstcapacity information and the second capacity information, that thesecond nDVR will not record the one or more content segments.
 3. Themethod of claim 1, further comprising: determining, by the first nDVRand based on the first capacity information and the second capacityinformation, that the second nDVR will record second one or more contentsegments and that the first nDVR will not record the second one or morecontent segments.
 4. The method of claim 1, further comprising: causingoutput, to one or more user devices, of the one or more contentsegments.
 5. The method of claim 1, further comprising: storing thefirst capacity information in a first portion of a data structure; andstoring the second capacity information in a second portion of the datastructure.
 6. The method of claim 1, wherein the utilization associatedwith the first nDVR comprises one or more of: a current disk writingactivity, a maximum disk writing activity capacity, a current diskreading activity, a maximum disk reading activity capacity, a currentnetwork activity, a maximum network activity capacity, a currentcomputing activity, or a maximum computing activity capacity.
 7. Themethod of claim 1, wherein the storing the one or more content segmentsis further based on one or more of: a content channel associated withthe first nDVR, a content channel associated with the one or morecontent segments, a geographic location of the first nDVR, a geographiclocation of one or more users requesting the one or more contentsegments, or the first nDVR already storing other content segmentsassociated with the one or more content segments.
 8. The method of claim1, wherein the one or more content segments are associated with one ormore of: a content item selected by a user for recording, previouslystored content that is to be archived, or previously stored content thatis to be moved to a media storage from which the content is availablefor playback.
 9. The method of claim 1, wherein the storing the one ormore content segments is further based on one or more issues associatedwith the second nDVR, wherein the one or more issues comprise one ormore of: a loss of communication between the first nDVR and the secondnDVR, an inability to satisfy one or more user recording requests, acurrent disk writing activity exceeding a disk writing activitythreshold value, a current disk reading activity exceeding a diskreading activity threshold value, a current network activity exceeding anetwork activity threshold value, a current computing activity exceedinga computing activity threshold value, a component failure, a networkfailure, an incapacity of the second nDVR, a failure to receive aheartbeat message from the second nDVR, or a failure to receive thirdcapacity information expected from the second nDVR.
 10. The method ofclaim 1, wherein, one or more of: the first nDVR is associated with afirst group of users and the second nDVR is associated with a secondgroup of users, or the first nDVR is at a first location and the secondnDVR is at a second location.
 11. The method of claim 1, wherein the oneor more content segments are associated with one or more of: videocontent, audio content, media content, stored content, recorded content,an audio program, a video program, an audio/video program, a contentitem, or a television show.
 12. A method comprising: receiving, by afirst network digital video recorder (nDVR), data indicating one or morecontent segments; determining, by the first nDVR, first capacityinformation indicating a utilization associated with the first nDVR;receiving, by the first nDVR, second capacity information indicating autilization associated with a second nDVR; and determining, by the firstnDVR and based on the first capacity information and the second capacityinformation, that the second nDVR will store the one or more contentsegments.
 13. The method of claim 12, further comprising: determining,by the first nDVR and based on the first capacity information and thesecond capacity information, that the first nDVR will not store the oneor more content segments.
 14. The method of claim 12, furthercomprising: storing, by the second nDVR, the one or more contentsegments.
 15. The method of claim 12, further comprising: causingoutput, by the second nDVR and to one or more user devices, of the oneor more content segments.
 16. The method of claim 12, furthercomprising: determining, by the first nDVR, that second one or morecontent segments are stored by the second nDVR, wherein the one or morecontent segments and the second one or more content segments areassociated with a common content item, and wherein the determining thatthe second nDVR will store the one or more content segments is furtherbased on the determining that the second one or more content segmentsare stored by the second nDVR.
 17. The method of claim 12, furthercomprising: storing, by the first nDVR and based on the first capacityinformation and the second capacity information, second one or morecontent segments associated with the one or more content segments,wherein the one or more content segments and the second one or morecontent segments comprise common video content at different videoresolutions.
 18. The method of claim 12, further comprising: storing, bythe first nDVR and based on the first capacity information, the secondcapacity information, and one or more issues associated with the secondnDVR, second one or more content segments, wherein the one or moreissues comprise one or more of: a loss of communication between thefirst nDVR and the second nDVR, an inability to satisfy one or more userrecording requests, a current disk writing activity exceeding a diskwriting activity threshold value, a current disk reading activityexceeding a disk reading activity threshold value, a current networkactivity exceeding a network activity threshold value, a currentcomputing activity exceeding a computing activity threshold value, acomponent failure, a network failure, an incapacity of the second nDVR,a failure to receive a heartbeat message from the second nDVR, or afailure to receive third capacity information expected from the secondnDVR.
 19. An apparatus comprising: one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the apparatus to: determine first capacity information indicatinga utilization associated with the apparatus; receive second capacityinformation indicating a utilization associated with a network digitalvideo recorder (nDVR); and store, based on the first capacityinformation and the second capacity information, one or more contentsegments.
 20. The apparatus of claim 19, wherein the instructions, whenexecuted by the one or more processors, further cause the apparatus to:determine, based on the first capacity information and the secondcapacity information, that the nDVR will not record the one or morecontent segments.
 21. The apparatus of claim 19, wherein theinstructions, when executed by the one or more processors, further causethe apparatus to: determine, based on the first capacity information andthe second capacity information, that the nDVR will record second one ormore content segments and that the apparatus will not record the secondone or more content segments.
 22. The apparatus of claim 19, wherein theinstructions, when executed by the one or more processors, further causethe apparatus to: cause output, to one or more user devices, of the oneor more content segments.
 23. The apparatus of claim 19, wherein theinstructions, when executed by the one or more processors, further causethe apparatus to: store the first capacity information in a firstportion of a data structure; and store the second capacity informationin a second portion of the data structure.
 24. The apparatus of claim19, wherein the utilization associated with the apparatus comprises oneor more of: a current disk writing activity, a maximum disk writingactivity capacity, a current disk reading activity, a maximum diskreading activity capacity, a current network activity, a maximum networkactivity capacity, a current computing activity, or a maximum computingactivity capacity.
 25. The apparatus of claim 19, wherein the storingthe one or more content segments is further based on one or more of: acontent channel associated with the apparatus, a content channelassociated with the one or more content segments, a geographic locationof the apparatus, a geographic location of one or more users requestingthe one or more content segments, or the apparatus already storing othercontent segments associated with the one or more content segments. 26.The apparatus of claim 19, wherein the one or more content segments areassociated with one or more of: a content item selected by a user forrecording, previously stored content that is to be archived, orpreviously stored content that is to be moved to a media storage fromwhich the content is available for playback.
 27. The apparatus of claim19, wherein the storing the one or more content segments is furtherbased on one or more issues associated with the nDVR, wherein the one ormore issues comprise one or more of: a loss of communication between theapparatus and the nDVR, an inability to satisfy one or more userrecording requests, a current disk writing activity exceeding a diskwriting activity threshold value, a current disk reading activityexceeding a disk reading activity threshold value, a current networkactivity exceeding a network activity threshold value, a currentcomputing activity exceeding a computing activity threshold value, acomponent failure, a network failure, an incapacity of the nDVR, afailure to receive a heartbeat message from the nDVR, or a failure toreceive third capacity information expected from the nDVR.
 28. Theapparatus of claim 19, wherein, one or more of: the apparatus isassociated with a first group of users and the nDVR is associated with asecond group of users, or the apparatus is at a first location and thenDVR is at a second location.
 29. The apparatus of claim 19, wherein theone or more content segments are associated with one or more of: videocontent, audio content, media content, stored content, recorded content,an audio program, a video program, an audio/video program, a contentitem, or a television show.
 30. An apparatus comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the apparatus to: receive data indicatingone or more content segments; determine first capacity informationindicating a utilization associated with the apparatus; receive secondcapacity information indicating a utilization associated with a networkdigital video recorder (nDVR); and determine, based on the firstcapacity information and the second capacity information, that the nDVRwill store the one or more content segments.
 31. The apparatus of claim30, wherein the instructions, when executed by the one or moreprocessors, further cause the apparatus to: determine, based on thefirst capacity information and the second capacity information, that theapparatus will not store the one or more content segments.
 32. Theapparatus of claim 30, wherein the instructions, when executed by theone or more processors, further cause the apparatus to: determine thatsecond one or more content segments are stored by the nDVR, wherein theone or more content segments and the second one or more content segmentsare associated with a common content item, and wherein the determiningthat the nDVR will store the one or more content segments is furtherbased on the determining that the second one or more content segmentsare stored by the nDVR.
 33. The apparatus of claim 30, wherein theinstructions, when executed by the one or more processors, further causethe apparatus to: store, based on the first capacity information and thesecond capacity information, second one or more content segmentsassociated with the one or more content segments, wherein the one ormore content segments and the second one or more content segmentscomprise common video content at different video resolutions.
 34. Theapparatus of claim 30, wherein the instructions, when executed by theone or more processors, further cause the apparatus to: store, based onthe first capacity information, the second capacity information, and oneor more issues associated with the nDVR, second one or more contentsegments, wherein the one or more issues comprise one or more of: a lossof communication between the apparatus and the nDVR, an inability tosatisfy one or more user recording requests, a current disk writingactivity exceeding a disk writing activity threshold value, a currentdisk reading activity exceeding a disk reading activity threshold value,a current network activity exceeding a network activity threshold value,a current computing activity exceeding a computing activity thresholdvalue, a component failure, a network failure, an incapacity of thenDVR, a failure to receive a heartbeat message from the nDVR, or afailure to receive third capacity information expected from the nDVR.35. A non-transitory computer-readable medium storing instructions that,when executed, cause: determining, by a first network digital videorecorder (nDVR), first capacity information indicating a utilizationassociated with the first nDVR; receiving, by the first nDVR, secondcapacity information indicating a utilization associated with a secondnDVR; and storing, by the first nDVR and based on the first capacityinformation and the second capacity information, one or more contentsegments.
 36. The non-transitory computer-readable medium of claim 35,wherein the instructions, when executed, further cause: determining, bythe first nDVR and based on the first capacity information and thesecond capacity information, that the second nDVR will not record theone or more content segments.
 37. The non-transitory computer-readablemedium of claim 35, wherein the instructions, when executed, furthercause: determining, by the first nDVR and based on the first capacityinformation and the second capacity information, that the second nDVRwill record second one or more content segments and that the first nDVRwill not record the second one or more content segments.
 38. Thenon-transitory computer-readable medium of claim 35, wherein theinstructions, when executed, further cause: causing output, to one ormore user devices, of the one or more content segments.
 39. Thenon-transitory computer-readable medium of claim 35, wherein theinstructions, when executed, further cause: storing the first capacityinformation in a first portion of a data structure; and storing thesecond capacity information in a second portion of the data structure.40. The non-transitory computer-readable medium of claim 35, wherein theutilization associated with the first nDVR comprises one or more of: acurrent disk writing activity, a maximum disk writing activity capacity,a current disk reading activity, a maximum disk reading activitycapacity, a current network activity, a maximum network activitycapacity, a current computing activity, or a maximum computing activitycapacity.
 41. The non-transitory computer-readable medium of claim 35,wherein the storing the one or more content segments is further based onone or more of: a content channel associated with the first nDVR, acontent channel associated with the one or more content segments, ageographic location of the first nDVR, a geographic location of one ormore users requesting the one or more content segments, or the firstnDVR already storing other content segments associated with the one ormore content segments.
 42. The non-transitory computer-readable mediumof claim 35, wherein the one or more content segments are associatedwith one or more of: a content item selected by a user for recording,previously stored content that is to be archived, or previously storedcontent that is to be moved to a media storage from which the content isavailable for playback.
 43. The non-transitory computer-readable mediumof claim 35, wherein the storing the one or more content segments isfurther based on one or more issues associated with the second nDVR,wherein the one or more issues comprise one or more of: a loss ofcommunication between the first nDVR and the second nDVR, an inabilityto satisfy one or more user recording requests, a current disk writingactivity exceeding a disk writing activity threshold value, a currentdisk reading activity exceeding a disk reading activity threshold value,a current network activity exceeding a network activity threshold value,a current computing activity exceeding a computing activity thresholdvalue, a component failure, a network failure, an incapacity of thesecond nDVR, a failure to receive a heartbeat message from the secondnDVR, or a failure to receive third capacity information expected fromthe second nDVR.
 44. The non-transitory computer-readable medium ofclaim 35, wherein, one or more of: the first nDVR is associated with afirst group of users and the second nDVR is associated with a secondgroup of users, or the first nDVR is at a first location and the secondnDVR is at a second location.
 45. The non-transitory computer-readablemedium of claim 35, wherein the one or more content segments areassociated with one or more of: video content, audio content, mediacontent, stored content, recorded content, an audio program, a videoprogram, an audio/video program, a content item, or a television show.46. A non-transitory computer-readable medium storing instructions that,when executed, cause: receiving, by a first network digital videorecorder (nDVR), data indicating one or more content segments;determining, by the first nDVR, first capacity information indicating autilization associated with the first nDVR; receiving, by the firstnDVR, second capacity information indicating a utilization associatedwith a second nDVR; and determining, by the first nDVR and based on thefirst capacity information and the second capacity information, that thesecond nDVR will store the one or more content segments.
 47. Thenon-transitory computer-readable medium of claim 46, wherein theinstructions, when executed, further cause: determining, by the firstnDVR and based on the first capacity information and the second capacityinformation, that the first nDVR will not store the one or more contentsegments.
 48. The non-transitory computer-readable medium of claim 46,wherein the instructions, when executed, further cause: storing, by thesecond nDVR, the one or more content segments.
 49. The non-transitorycomputer-readable medium of claim 46, wherein the instructions, whenexecuted, further cause: causing output, by the second nDVR and to oneor more user devices, of the one or more content segments.
 50. Thenon-transitory computer-readable medium of claim 46, wherein theinstructions, when executed, further cause: determining, by the firstnDVR, that second one or more content segments are stored by the secondnDVR, wherein the one or more content segments and the second one ormore content segments are associated with a common content item, andwherein the determining that the second nDVR will store the one or morecontent segments is further based on the determining that the second oneor more content segments are stored by the second nDVR.
 51. Thenon-transitory computer-readable medium of claim 46, wherein theinstructions, when executed, further cause: storing, by the first nDVRand based on the first capacity information and the second capacityinformation, second one or more content segments associated with the oneor more content segments, wherein the one or more content segments andthe second one or more content segments comprise common video content atdifferent video resolutions.
 52. The non-transitory computer-readablemedium of claim 46, wherein the instructions, when executed, furthercause: storing, by the first nDVR and based on the first capacityinformation, the second capacity information, and one or more issuesassociated with the second nDVR, second one or more content segments,wherein the one or more issues comprise one or more of: a loss ofcommunication between the first nDVR and the second nDVR, an inabilityto satisfy one or more user recording requests, a current disk writingactivity exceeding a disk writing activity threshold value, a currentdisk reading activity exceeding a disk reading activity threshold value,a current network activity exceeding a network activity threshold value,a current computing activity exceeding a computing activity thresholdvalue, a component failure, a network failure, an incapacity of thesecond nDVR, a failure to receive a heartbeat message from the secondnDVR, or a failure to receive third capacity information expected fromthe second nDVR.
 53. A system comprising: a first network digital videorecorder (nDVR); and a second nDVR, and wherein the first nDVR isconfigured to: determine first capacity information indicating autilization associated with the first nDVR; receive second capacityinformation indicating a utilization associated with the second nDVR;and store, based on the first capacity information and the secondcapacity information, one or more content segments.
 54. The system ofclaim 53, wherein the first nDVR is further configured to: determine,based on the first capacity information and the second capacityinformation, that the second nDVR will not record the one or morecontent segments.
 55. The system of claim 53, wherein the first nDVR isfurther configured to: determine, based on the first capacityinformation and the second capacity information, that the second nDVRwill record second one or more content segments and that the first nDVRwill not record the second one or more content segments.
 56. The systemof claim 53, wherein the first nDVR is further configured to: causeoutput, to one or more user devices, of the one or more contentsegments.
 57. The system of claim 53, wherein the first nDVR is furtherconfigured to: store the first capacity information in a first portionof a data structure; and store the second capacity information in asecond portion of the data structure.
 58. The system of claim 53,wherein the utilization associated with the first nDVR comprises one ormore of: a current disk writing activity, a maximum disk writingactivity capacity, a current disk reading activity, a maximum diskreading activity capacity, a current network activity, a maximum networkactivity capacity, a current computing activity, or a maximum computingactivity capacity.
 59. The system of claim 53, wherein the first nDVR isfurther configured to store the one or more content segments furtherbased on one or more of: a content channel associated with the firstnDVR, a content channel associated with the one or more contentsegments, a geographic location of the first nDVR, a geographic locationof one or more users requesting the one or more content segments, or thefirst nDVR already storing other content segments associated with theone or more content segments.
 60. The system of claim 53, wherein theone or more content segments are associated with one or more of: acontent item selected by a user for recording, previously stored contentthat is to be archived, or previously stored content that is to be movedto a media storage from which the content is available for playback. 61.The system of claim 53, wherein the first nDVR is further configured tostore the one or more content segments further based on one or moreissues associated with the second nDVR, wherein the one or more issuescomprise one or more of: a loss of communication between the first nDVRand the second nDVR, an inability to satisfy one or more user recordingrequests, a current disk writing activity exceeding a disk writingactivity threshold value, a current disk reading activity exceeding adisk reading activity threshold value, a current network activityexceeding a network activity threshold value, a current computingactivity exceeding a computing activity threshold value, a componentfailure, a network failure, an incapacity of the second nDVR, a failureto receive a heartbeat message from the second nDVR, or a failure toreceive third capacity information expected from the second nDVR. 62.The system of claim 53, wherein, one or more of: the first nDVR isassociated with a first group of users and the second nDVR is associatedwith a second group of users, or the first nDVR is at a first locationand the second nDVR is at a second location.
 63. The system of claim 53,wherein the one or more content segments are associated with one or moreof: video content, audio content, media content, stored content,recorded content, an audio program, a video program, an audio/videoprogram, a content item, or a television show.
 64. A system comprising:a first network digital video recorder (nDVR); and a second nDVR, andwherein the first nDVR is configured to: receive data indicating one ormore content segments; determine first capacity information indicating autilization associated with the first nDVR; receive second capacityinformation indicating a utilization associated with the second nDVR;and determine, based on the first capacity information and the secondcapacity information, that the second nDVR will store the one or morecontent segments.
 65. The system of claim 64, wherein the first nDVR isfurther configured to: determine, based on the first capacityinformation and the second capacity information, that the first nDVRwill not store the one or more content segments.
 66. The system of claim64, wherein the second nDVR is configured to: store the one or morecontent segments.
 67. The system of claim 64, wherein the second nDVR isconfigured to: cause output, to one or more user devices, of the one ormore content segments.
 68. The system of claim 64, wherein the firstnDVR is further configured to: determine that second one or more contentsegments are stored by the second nDVR, wherein the one or more contentsegments and the second one or more content segments are associated witha common content item, and wherein the determining that the second nDVRwill store the one or more content segments is further based on thedetermining that the second one or more content segments are stored bythe second nDVR.
 69. The system of claim 64, wherein the first nDVR isfurther configured to: store, based on the first capacity informationand the second capacity information, second one or more content segmentsassociated with the one or more content segments, wherein the one ormore content segments and the second one or more content segmentscomprise common video content at different video resolutions.
 70. Thesystem of claim 64, wherein the first nDVR is further configured to:store, based on the first capacity information, the second capacityinformation, and one or more issues associated with the second nDVR,second one or more content segments, wherein the one or more issuescomprise one or more of: a loss of communication between the first nDVRand the second nDVR, an inability to satisfy one or more user recordingrequests, a current disk writing activity exceeding a disk writingactivity threshold value, a current disk reading activity exceeding adisk reading activity threshold value, a current network activityexceeding a network activity threshold value, a current computingactivity exceeding a computing activity threshold value, a componentfailure, a network failure, an incapacity of the second nDVR, a failureto receive a heartbeat message from the second nDVR, or a failure toreceive third capacity information expected from the second nDVR.